Repository navigation
chore(renovate): automerge minor and patch dev dependency updates - #31533
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
2 participants
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.
Issue number: internal
What is the current behavior?
Every Renovate PR needs a manual approval and merge, including frequent low-risk bumps like
vitest,@types/nodeandgithub/codeql-actionthat we always merge as-is.What is the new behavior?
Minor and patch updates for
vitest, the Playwright group,@types/node,github/codeql-actionandactions/*now automerge once CI passes. Majors still open as normal PRs that need a review. A Playwright bump that changes rendering failsverify-screenshots, so it'll wait for a person the same as before.platformAutomergeis off, so Renovate merges the PR itself and waits for every check on the branch rather than relying on GitHub's native auto-merge.Does this introduce a breaking change?
Other information