Repository navigation
ci(release): pin changesets/action v2 and use its renamed inputs - #28
Merged
Merged
Conversation
changesets/action renamed its inputs and moved the v1 tag forward to that release, so the pinned v1 now rejects the old keys. Pin to v2 and rename version -> version-script and publish -> publish-script.
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.
Fixes the failing Release workflow.
changesets/actionrenamed its inputs and moved thev1tag forward to that release, so the pinned@v1action rejects the oldversion/publishkeys. Pins the action to@v2and renames the inputs toversion-script/publish-script, matching the utils repo.Closes #27