Fix pnpm setup order to follow official documentation #32
Conversation
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
gndelia
requested review from
ArturDolzan,
arielmergen,
gabmontes and
joshuasing
4 tasks
joshuasing
approved these changes
Jan 30, 2026
ArturDolzan
approved these changes
Jan 30, 2026
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 fix updates the GitHub Actions workflow to follow the official pnpm documentation for CI/CD setup as described in https://pnpm.io/continuous-integration#github-actions.
Changes
The key change is installing pnpm before setting up Node.js, which is the recommended approach in the pnpm docs. This ensures pnpm is available when
actions/setup-nodeattempts to use it for caching.What changed
pnpm/action-setupstep beforeactions/setup-nodeinsetup-node-env/action.ymlThis aligns our workflow with the standard pnpm + GitHub Actions integration pattern.