fix: Remove redundant npm publish from auto-release#750
Closed
JakeCooper wants to merge 1 commit intomasterfrom
Closed
fix: Remove redundant npm publish from auto-release#750JakeCooper wants to merge 1 commit intomasterfrom
JakeCooper wants to merge 1 commit intomasterfrom
Conversation
The release.yml workflow already handles npm publishing with OIDC when the tag is pushed. No need to duplicate it in auto-release. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Contributor
Author
|
Superseded by #751 which moves crates.io publish to release.yml for parallelization |
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.
Summary
Remove npm publish steps from auto-release.yml - they're already handled by release.yml via OIDC when the tag is pushed.
The flow is:
🤖 Generated with Claude Code