-
Notifications
You must be signed in to change notification settings - Fork 70
chore(pinact): pin/update GitHub Actions #448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
davidliu
wants to merge
1
commit into
main
Choose a base branch
from
ci/pinact_action
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Release workflow fails before publishing
Every release run using
changesets/actionv2.1.0 rejects the installed Changesets CLI v2.29.8. The legacyversionandpublishinputs also fail v2 validation.Learn more
Changesets Action v2 requires Changesets CLI v3 and validates that requirement before selecting release mode. This repository declares
@changesets/cli2.29.8 in package dependencies, so each run exits before creating a version pull request or publishing. After upgrading the CLI, the action still rejects the old workflow input names because v2 renamed them toversion-scriptandpublish-script. The token configuration also needs migration to thegithub-tokeninput if a custom token is intended; setting onlyGITHUB_TOKENno longer configures v2.Example: A push to
mainstarts Release. Dependency installation provides Changesets CLI 2.29.8, then the action reports that CLI v2 is unsupported and publishes nothing.Recommended fix: Either retain Changesets Action v1, or migrate the repository atomically to Changesets CLI v3. For v2, rename
versiontoversion-scriptandpublishtopublish-script, and pass any custom token throughgithub-token. Verify thatci:publishpreservesCHANGESETS_OUTPUTso the action can detect published packages.Was this helpful? React with 👍 or 👎 to provide feedback.