fix: publish v0.6.1 directly to latest - #53
Merged
Merged
Conversation
Signed-off-by: David Ahmann <46606159+davidahmann@users.noreply.github.com>
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.
This releases a fresh
0.6.1source candidate that publishes directly to npmlatestthrough the existing protected OIDC workflow. It leaves the published0.6.0package and its unchanged channels intact.The README now tells users to inspect live provider evidence and pin an exact release version. Release documentation assigns final provider facts to the workflow-attached
release-evidence-final.json, eliminating a post-release documentation-only PR. The workflow policy now rejects making the GitHub release public before final evidence is attached.Validation:
npm run check(367 tests, coverage, packed lifecycle canary)node dist/cli.js --json --cwd . audit