Repository navigation
fix: hold moved library releases from consumers on the old paths - #352
Merged
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
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.
On
dev, Renovate follows first-party pre-releases even from a stable pin. web-terminal-enginev6.5.0-dev.2now requiresgithub.com/cplieger/go/textsafe, while marotte and web-terminal-kiro still require the old library paths, so the next bump would build both paths of one library into each. This rule holds the engine's Go module and its npm pair (@cplieger/web-terminal-engine,@cplieger/web-terminal-ui) ondevfor those two repositories only, until each moves to the new paths and takes the held versions in the same change. Other repositories andmainare unaffected.renovate-config-validatorpasses ontwo-branch.json.