Repository navigation
fix(release): diagnose OIDC and retry immutable SDK tags - #7
Merged
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.
SDK 0.2.0 passed release validation, but npm rejected publication with a masked 404 despite a valid trusted-publisher entry. Add an OIDC preflight that reports the failing authentication boundary without logging credentials.
Allow manual recovery from main using an existing SDK tag. Verify the tag resolves to the checkout, the revision belongs to main, all SDK versions match, and the complete original quality gates pass. Publish that exact verified revision; never move release tags.
Validation: YAML parsing, identity-guard assertions, syntax checks for all eight shell steps and the embedded Node preflight, Prettier, and git diff checks passed.