Usually no. A fix bot should meet the same required reviews and checks as a person, because bypass rights turn its mistakes into merged code. If you do add it to a bypass list, do it for a narrow, documented reason, and keep the checks that still apply.
What a bypass list changes
Branch protection and rulesets define what must be true before code lands: reviews, status checks, merge methods. A bypass list names actors who may skip some of those rules. Putting a bot there says its changes need less scrutiny than a person's. That is the opposite of what you want for a tool that reads public package data and writes to your repository.
When it comes up
Renovate's documentation mentions bypass lists in two places. With a GitHub merge queue and platform automerge turned off, Renovate first tries to merge the PR directly, which succeeds when Renovate is on the merge queue's bypass list. If the merge is refused and the base branch has a merge queue, Renovate adds the PR to the queue itself once checks pass. The documentation also warns that branch automerge only works with a merge queue when Renovate is on the bypass list, because pushing directly to the base branch is not possible otherwise; otherwise it falls back to creating a PR, and it recommends the PR automerge type in such repositories or adding Renovate to the bypass list.
So the documented defaults and the queue route work without a bypass. The bypass is an optional shortcut, not a requirement.
A decision guide
| Question | If yes | If no |
|---|---|---|
| Does the bot only open PRs? | No bypass needed | Review what else it does |
| Do PRs go through the merge queue? | No bypass needed | Consider PR automerge, not branch automerge |
| Would a bypass skip required review? | Do not grant it | Fine if only a mechanical step is skipped |
| Is the reason written down and reviewed? | Acceptable | Do not grant it |
Risks of a bypass
- Mistakes merge faster. A buggy rule or a bad release lands without the checks that would have caught it.
- Compromise has more reach. If the bot's token leaks, an attacker inherits the bypass. See least privilege token permissions for security automation.
- Evidence weakens. An auditor sees that a class of changes skipped review.
Safer alternatives
Let the bot open PRs, require checks, and let a platform feature merge them after rules pass. That keeps the rules in force. Give the bot its own identity and signed commits so its work is traceable: see give a fix bot its own identity and signed commits. Reduce the speed problem with grouping and schedules instead of loosening rules.
If you must bypass
- Scope it to one repository and one branch.
- Keep required status checks in force.
- Write down who approved it and the date.
- Set a review date.
- Log merges by the bot and sample them monthly.
Check regularly
Bypass lists grow over time. List them each quarter, and ask of each entry whether it is still needed. A short list that people can explain is easier to defend than a long one nobody remembers. See also do update bots work with merge queues and merge trains.
Try it yourself
Open the demo and see which rules decide whether a change may merge. Consider what changes if an actor can skip them.
Click through it at your own pace, or open it full screen.
Safeguard can open fix pull requests through autonomous remediation. It is off by default and every category starts on Manual, so a person approves each change. You can also run a free scan to see which dependencies have known fixes before you decide what to automate.
Quick check
Does Renovate require a bypass to use a merge queue?
The documentation describes a route where Renovate adds the PR to the queue itself, which does not need a bypass. Branch automerge with a queue does.
Is a bot with bypass rights a security risk?
It increases the impact of a bot mistake or a leaked token, so keep it narrow and reviewed.
Sources
Last reviewed: 19 October 2026.
