Repository navigation
ci: add the Update PNPM workflow - #216
Merged
Merged
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
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.
Adds a weekly workflow that updates the pnpm version pinned in
package.jsonand opens a PR with the change.The steps live in the shared workflow in streetsidesoftware/actions, callable at
@v1since release 1.7.0. This repo only holds the triggers:What to expect
pnpm self-updategoes tolatest. On a pnpm 11 lockfile it also adds a second YAML document that records the pnpm version.minimumReleaseAgein this repo'spnpm-workspace.yaml.packageManagerfield loses its+sha512…suffix. The lockfile still holds the integrity hashes of the pnpm packages.Verification
main, so the first run comes after this PR is merged.