chore(deps): pnpm security bump 11.8.0 → 11.11.0 - #1398
Open
apify-deps[bot] wants to merge 1 commit into
Open
Conversation
![apify-deps[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…ar override Fixes GHSA advisory for pnpm < 11.11.0 (alerts #276-278) by aligning devEngines.packageManager with the already-bumped packageManager field, which regenerates the packageManagerDependencies pins in the lockfile. Also drops the pnpm-workspace.yaml `tar` override: tar is no longer present in the dependency tree, so the pin was a no-op.
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
2 participants
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.
Summary
Dependency sweep — targeted security bumps only (this repo has
lockfileRefresh: false, so no broad freshening pass):pnpm(self-managed viadevEngines.packageManager) 11.8.0 → 11.11.0 (high — alert #276, alert #277, alert #278)package.json'spackageManagerfield was alreadypnpm@11.11.0, butdevEngines.packageManager.versionwas still11.8.0— pnpm uses the latter to resolve its ownpackageManagerDependenciespin in the lockfile, so the vulnerable 11.8.0 stayed locked despite the top-level field being current. Aligned both to 11.11.0, which regenerates the pin.pnpm-workspace.yamlalready carries aminimumReleaseAgeExcludeentry forpnpm@11.11.0(added by Renovate), so the supply-chain policy check passes.🧹 Pruned overrides (no longer needed)
tar(pinned to7.5.16) — no longer present anywhere in the dependency tree (pnpm why tar -ris empty); the pin was a no-op. Removing it only produces peer-key bookkeeping churn in the lockfile, no version changes.🤖 Generated with Claude Code