fix: prevent release failure when SDK version already published#145
Merged
Conversation
The release script runs `npm publish` for the SDK sub-package after `changeset publish`. If the SDK version is already on npm (e.g. from a prior release run), npm returns 403 and fails the whole CI job. Redirect stderr and fall back gracefully so the Release action stays green on re-runs.
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.
The release script runs
npm publishfor the SDK sub-package afterchangeset publish. If the SDK version is already on npm (e.g. from a prior release run), npm returns 403 and fails the whole CI job.Redirect stderr and fall back gracefully so the Release action stays green on re-runs.
Fixes the failing Release action: https://github.com/ReScienceLab/agent-world-network/actions/runs/23436588741