Repository navigation
chore: bump library patch version to 16.3.17 - #368
Draft
marceloneppel wants to merge 1 commit into
Draft
marceloneppel wants to merge 1 commit into
marceloneppel wants to merge 1 commit into
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
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.
Issue
The final charm->library migration slices (the VM stack #355-#361 and the K8s stack #362-#367) all landed on 16.3.16; the merge target for the charm consumption PRs needs a distinct version marker containing ALL of them.
Solution
pyproject.toml: version 16.3.16 -> 16.3.17.uv.lock: the single root-package version line regenerated with the repo's own lock generator (diff confined to that line).Checklist