chore(deps): update pnpm/action-setup action to v6 - abandoned#620
Open
renovate[bot] wants to merge 2 commits intomainfrom
Open
chore(deps): update pnpm/action-setup action to v6 - abandoned#620renovate[bot] wants to merge 2 commits intomainfrom
renovate[bot] wants to merge 2 commits intomainfrom
Conversation
renovate
Bot
changed the title
Contributor
Author
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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 PR contains the following updates:
v3→v6Release Notes
pnpm/action-setup (pnpm/action-setup)
v6.0.0Compare Source
v5.0.0Compare Source
Updated the action to use Node.js 24.
v4.4.0Compare Source
Updated the action to use Node.js 24.
v4.3.0Compare Source
What's Changed
@types/node-fetchdependency by @silverwind in #186New Contributors
Full Changelog: pnpm/action-setup@v4.2.0...v4.3.0
v4.2.0Compare Source
When there's a
.npmrcfile at the root of the repository, pnpm will be fetched from the registry that is specified in that.npmrcfile #179v4.1.0Compare Source
Add support for
package.yaml#156.v4.0.0Compare Source
An error is thrown if one version of pnpm is specified in the
packageManagerfield ofpackage.jsonand a different version is specified in the action's settings #122Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.
Note
Medium Risk
Primarily impacts build/release automation; the major
pnpm/action-setupbump and lockfile format/toolchain metadata change could cause CI/deploy failures if pnpm resolution or caching behavior differs.Overview
CI, release, deploy, and autofix GitHub Actions workflows now use
pnpm/action-setup@v6(fromv3) everywhere pnpm is installed.The
pnpm-lock.yamlis updated to includepackageManagerDependencies/@pnpm/exeentries and a new leading lockfile document for the pinned pnpm toolchain, which may affect how pnpm is resolved in automation.Reviewed by Cursor Bugbot for commit 26866a3. Bugbot is set up for automated code reviews on this repo. Configure here.