chore: refresh published bot IP ranges - #26
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
chore/refresh-bot-ranges
branch
from
August 17, 2026 06:05
c9af4fc to
5825a24
Compare
github-actions
Bot
force-pushed
the
chore/refresh-bot-ranges
branch
from
August 24, 2026 06:08
5825a24 to
bfa0a8c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated weekly refresh of
src/bot-ranges.tsfrom the vendors'published crawler feeds.
Review the prefix diff before merging. Ranges that disappear
upstream will start producing
spoofedverdicts for traffic thatwas previously
verified, so a large removal is worth a secondlook rather than a reflex merge.
The refresh script already refuses to write a list that shrinks by
more than half or when any feed errors, and the test suite has run
against this snapshot.
Merging does not publish — bump
package.jsonseparately when youwant the new ranges to reach consumers.