chore(deps): dependency sweep — pnpm security bumps + in-range freshening - #1446
Open
apify-deps[bot] wants to merge 1 commit into
Open
apify-deps[bot] wants to merge 1 commit into
apify-deps[bot] wants to merge 1 commit into
Conversation
![apify-deps[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…ning - devEngines.packageManager pnpm 11.8.0 -> 11.11.0, fixing the version mismatch that made corepack ignore packageManager and lock the self-managed pnpm binary to a vulnerable 11.x release (3 high-severity advisories: virtual-store path traversal, tarball-manifest arbitrary file write, env-secret exfiltration via proxy placeholder expansion). - pnpm update -r: broad in-range lockfile refresh/freshening. - Drop the now-redundant tar override in pnpm-workspace.yaml -- no tar package remains anywhere in the resolved tree.
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 — security bumps + in-range freshening (all within existing ranges):
pnpm(self-managed viadevEngines.packageManager/ lockfilepackageManagerDependencies) 11.8.0 → 11.11.0 (high) — fixes 3 advisories: virtual-store linker path traversal, tarball-manifest arbitrary file write, and env-secret exfiltration via proxy placeholder expansion.devEngines.packageManager.versionwas lagging behindpackageManager/volta.pnpm(already11.11.0), which made corepack ignorepackageManagerand pin installs to the vulnerable11.8.0. (alert #278, alert #277, alert #276)pnpm update -r: broad in-range lockfile refresh/freshening (patch + minor bumps acrosspackage.jsonranges and the lockfile —axios,@crawlee/*,execa,adm-zip,@inquirer/*, docs-site@docusaurus/*/react, etc.).🧹 Pruned overrides (no longer needed)
tar(pnpm-workspace.yamloverride, pinned to7.5.22) — no-op: notarpackage remains anywhere in the resolved dependency tree (root orwebsite/).✅ Dismissed (don't apply to our usage)
None — all 3 open alerts were the same
pnpmissue, fixed above.🤖 Generated with Claude Code