chore: verify OIDC trusted publishing to npm - #123
Merged
Merged
Conversation
No code change. Forces a release so the new publish.yml is exercised end to end with npm trusted publishing. Release-As: 5.5.1 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.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
2 participants
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
Empty commit carrying a
Release-As: 5.5.1footer. No code change.Merging this makes Release Please open a
release: 5.5.1PR. Merging that one creates the GitHub release, which triggers the renamedpublish.ymland exercises npm OIDC trusted publishing end to end for the first time (#122).Merge with a merge commit, not squash, so the commit with the
Release-Asfooter lands onmasteras is.If the publish fails, the release still exists; fix
publish.ymland use "Re-run failed jobs" on that run.🤖 Generated with Claude Code