Set changesets GitHub action to v1.5.1 to fix a failing step in our release flow#358
Merged
rochlefebvre merged 1 commit intomainfrom Jun 6, 2025
Conversation
gabypancu
approved these changes
Jun 6, 2025
Contributor
Author
1 task
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
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.

What are you trying to accomplish?
We currently cannot release a new version of our gem due to an error in the npm release flow.
Create release Pull Request or publish to NPM step
I found this existing bug on the action's repo. Users are rolling back to an older version until a fix such as this one restores proper support for the
cwdaction param.What approach did you choose and why?
Pin to 1.5.1 which seems to have worked for others.
Testing
We'll see what happens during the release process!
Checklist