feat(cloud): add reproducible stack compatibility lock - #29
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.
Summary
Compatibility evidence
Lock digest:
sha256:ce9ebd3af1cd5a2c972bd5f9e553bb9e77614b6b31bf03fe205a721d9097fe99The lock aligns Gateway 1.0.12 with ACL 0.2.2 and Updater 0.3.0. It also aligns the optional Gateway wire surface with Sentry 0.7.0.
Validation
just cloud-stack-checkcargo check --workspace --all-targets --lockedpassedcargo check --locked --all-targets --features wirepassedThis is the first verifiable clean-checkout compatibility-lock slice for #21. It intentionally leaves the issue open for broader release publication evidence and any future cross-repository service fixtures.