Repository navigation
feat(renovate): hold every toolbelt update in marotte - #472
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.
toolbelt's httpserver v2 port ships as a v3 minor, not a v4 major, so the rule from #470 (the toolbelt/v3 major disabled in marotte and web-terminal-kiro) would let it through. This replaces that rule: every
github.com/cplieger/toolbelt/v3update is disabled in marotte, which takes toolbelt by hand with its own httpserver v2 move and removes the rule then. web-terminal-kiro leaves the rule, because its httpserver v2 port takes the new toolbelt in the same change.Checked with the Renovate container's validator (
--strict, plus a broken key that it refuses) andapplyPackageRules: a toolbelt/v3 minor and major are disabled in marotte; a minor in web-terminal-kiro and in grelot is untouched.