chore: Add shared version control for all implementations of pnpm
#529
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.
Purpose 馃幆
Version management for the Github action
pnpm/action-setup
has been added via a regexManager rule. In addition to this, a packageRule forpnpm
has been added to bring allpnpm
versioning together. The regexManager rule is based on a pre-existing pattern made by renovate.This change has been added due to a limitation of the action not having a means to specify a directory where a
package.json
can live. This means rather than relying on the versioning of a package manager specified in there, a version has to be set for the action.Context 馃
pnpm
was updating in all places but the Github action.Notes 馃摀
autoMerge
set tofalse
for now. This is to confirm thatpnpm
works predictably in Github Actions when updates are released. Unfortunately, despite failing tests, thepnpm
updates were merged anyway.pnpm/action-setup
. Refer to: Parse package.json from subfolder聽pnpm/action-setup#83