deps: renovate-manage the anolis version pin; bump to current#26
Merged
Conversation
schemas/anolis-version.json was hand-maintained and stale (anolis 0.1.5 / protocol 1.1.4 vs live 0.1.26 / 1.6.0). Keep the pin — it is this repo's own dependency declaration, giving reviewable bumps and reproducible builds — but stop maintaining it by hand: - add regex customManagers (github-releases datasource) so Renovate bumps both keys, grouped into one PR - bump to anolis 0.1.26 / anolis-protocol 1.6.0; full docs build verified against the new schema tarballs and protocol tag Closes #25.
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.
What
renovate.json: two regexcustomManagers(github-releases datasource) coveringschemas/anolis-version.json—anolis_version→anolishq/anolis,anolis_protocol_version→anolishq/anolis-protocol; grouped into a single "anolis version pin" PR. Same pattern as anolis-projects' machine-profile manager.Why
The pin was hand-maintained → stale. Keeping a pin (vs deriving latest at build time) keeps docs builds reproducible and bumps reviewable; Renovate removes the hand-maintenance. Amended scope agreed on #25.
Verification
Full
npm run buildgreen against the new pins: all four v0.1.26 schema tarballs injected, protocol reference generated at v1.6.0, vitepress build complete.Closes #25.