Widen oa-configurator pin to a semver range#25
Open
nicoloesch wants to merge 2 commits into
Open
Conversation
nicoloesch
changed the title
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.
oa-configuratorpin to a semver range #24.Now that centralised CI/CD (#21) enforces semver-by-label upstream,
oa-configuratoronly bumps MAJOR when a PR is labelledbreaking. Replaces the exact==0.1.2pin with a range that tracks any compatible MINOR/PATCH release while still blocking a future MAJOR bump until it's explicitly reviewed.Also installs the
cava-devopspre-commit hook, so future dependency edits keepuv.locksurgically in sync without relying on memory:No behavioural change to the resolved version at merge time.
Notes
CI on this PR will fail until cava-devops PR AustralianCancerDataNetwork/cava-devops#2 merges to main
ci.ymlhere already points at@mainfor the--frozen-basedbuild-test-postgres.yml, which doesn't exist there yet. This is expected and will resolve on its own once that PR merges; no action needed here beyond waiting.