Repository navigation
Prepare PIG 0.3.6 with durable stable promotion - #51
Merged
Merged
Conversation
adit-chandra
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
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.
Prepare PIG 0.3.6 for an AWS-only release with schema-5 cloud enrollment and the merged supervisor security fixes. Package, chart, and requirements versions align before building the immutable candidate.
Promotion first merges the accepted manifest into main, then opens a separate stable-selection PR referencing that retained commit. This preserves immutable manifest URLs when the repository uses squash or rebase merges and lets interrupted publication resume either phase without rewriting published refs.
Validation: 139 Python tests passed (2 environment-dependent skips), Ruff and whitespace checks passed. The promotion suite exercises actual Git repositories, both squash merges and branch deletion, retry after interrupted PR creation, mismatched bytes and catalog entries, closed PRs, and unrelated changes. Release acceptance and publication are separate gates after the exact candidate is built.