Run the publish command in a separate step #6721
Merged
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.
WHY are these changes introduced?
Continuation of #6713
The
changeset-releaseGitHub Action job keeps failing withAccess token expired or revokedwhen trying to publish packages, while themanual-cron-releasejob works correctly.The only difference was the command to publish, so maybe the
changesets/actionis not properly passing through the OIDC authentication environment when executing the publish command internally.WHAT is this pull request doing?
Splits the changesets action responsibilities:
changesets/actionnow only handles creating/updating version PRspnpm release latestdirectly (matching the workingmanual-cron-releasejob)How to test your changes?
Merge and retry
Measuring impact
How do we know this change was effective? Please choose one:
Checklist