chore: auto-update internal @rendobar deps on publish#72
Merged
Conversation
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.
Renovate already automerges minor/patch bumps, but only within the weekly window (
before 6am on Monday). That delays first-party@rendobar/*updates (most importantly@rendobar/sdk) by up to a week after an npm publish.This adds one packageRule, scoped to
@rendobar/**, that overrides the global schedule withat any timeand automerges patch/minor. Result: when a new SDK version publishes, the bump PR opens and self-merges within minutes instead of waiting for Monday. Major@rendobar/*bumps still fall through to the existing major rule (no automerge, labelled for review).No effect on third-party deps — they stay on the weekly batch.