Remove explicit pnpm version specification from workflows#170
Merged
Conversation
|
ilfa
previously approved these changes
Jul 2, 2026
necipallef
reviewed
Jul 2, 2026
Contributor
pnpm exec changesetto create a changeset. |
Contributor
This PR will not create a new release 🚀
|
Contributor
Coverage report
Test suite run success15 tests passing in 7 suites. Report generated by 🧪jest coverage report action from 5b00fe4 Show full coverage report
|
erayaydin
approved these changes
Jul 2, 2026
necipallef
approved these changes
Jul 2, 2026
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.
This pull request removes the explicit pnpm version specification from workflows to improve flexibility and compatibility with different environments. When the
versionfield is not provided, thepnpm/action-setupwill use thepackageManagerproperty frompackage.json