fix(renovate): group the web-terminal engine+ui npm pair across update types#87
Merged
Merged
Conversation
…e types web-terminal-ui declares the engine as a caret peerDependency, so the pair is only npm-resolvable in matching versions. Renovate bumping one side alone (engine major + ui minor after engine v3 shipped) made every consumer lockfile refresh fail with 'Lock file error - aborting', stalling ALL Renovate updates on vibekit and web-terminal-kiro. One group with separateMajorMinor=false moves the pair in a single branch; matchDepNames keeps the engine repo's frozen -v3 compat alias out of the group. Automerge semantics unchanged (a major in the pair still gates manually).
cplieger
enabled auto-merge (rebase)
July 19, 2026 21:38
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.
web-terminal-ui declares the engine as a caret peerDependency, so the pair is only npm-resolvable in matching versions. Renovate bumping one side alone (engine major + ui minor after engine v3 shipped) made every consumer lockfile refresh fail with 'Lock file error - aborting', stalling ALL Renovate updates on vibekit and web-terminal-kiro. One group with separateMajorMinor=false moves the pair in a single branch; matchDepNames keeps the engine repo's frozen -v3 compat alias out of the group. Automerge semantics unchanged (a major in the pair still gates manually).