chore(gds): regenerate the bundle lock onto content-addressed provenance - #46
Merged
Merged
Conversation
The control plane now identifies a bundle by the digest of its source tree rather than the commit that carried it, so a lock generated before that change names an identity its siblings can no longer match. Regenerate from the current control-plane state.
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.
The control plane now identifies a bundle by the digest of its source tree rather than the commit that carried it. A lock generated before that change names an identity its siblings cannot match, which
test_all_gds_projections_share_the_root_bundle_sourcecorrectly rejects.Regenerated from the current control-plane state; all active modules and the superproject now share one
source_tree_digest.