Repository navigation
chore(deps): security + in-range lockfile refresh - #398
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
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
apify-deps
Bot
force-pushed
the
chore/deps-sweep
branch
2 times, most recently
from
November 13, 2026 00:25
c310b59 to
84b83c4
Compare
Contributor
Author
|
🔄 sweep re-run 2026-11-13: re-audited overrides (kept js-yaml, dropped the no-op crawlee-v4-beta pins), re-confirmed all 15 open alerts are CAPPED (no change in fix count: 0 fixed / 0 dismissed / 15 flagged). |
Dependabot alerts remain CAPPED by consumer-pinned ranges (nx, crawlee v4-beta stack, get-uri) — see PR body. In-range freshening only: @apify/* patch bumps, broad pnpm update -r, and pruning the no-op crawlee@4-beta workspace override (sitemap-scraper already pins it directly).
apify-deps
Bot
force-pushed
the
chore/deps-sweep
branch
from
November 16, 2026 00:25
84b83c4 to
5cee884
Compare
Contributor
Author
|
🔄 sweep re-run 2026-11-16: 0 fixed / 0 dismissed / 16 flagged (all CAPPED by consumer-pinned ranges — nx/lerna, crawlee v4-beta stack, get-uri); freshening only (@apify/* patch bumps, broad refresh, 1 stale override pruned). New alert since last run: #406 (basic-ftp). |
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.
Summary
Dependency sweep — in-range freshening (no alert could be resolved in-range this run; all 16 are CAPPED, see 🚩 below):
@apify/consts^3.0.1→^3.1.0@apify/input_secrets^2.0.8→^2.0.9@apify/log^3.0.1→^3.0.2(root +packages/scraper-tools)apify-client^2.25.0→^2.26.0pnpm update -rlockfile refresh (transitive/peer patch+minor bumps:axios→ 1.21.1,follow-redirects→ 1.16.3,js-yaml(cosmiconfig copy) → 5.5.0,ansi-regex→ 6.6.0,lilconfig→ 3.1.5,glob→ 14.0.6,fingerprint-generator/header-generator/generative-bayesian-network/fingerprint-injector→ 2.1.90,nx→ 23.3.2,vite→ 8.3.8, plus routinecaniuse-lite/electron-to-chromium/tldtschurn)🧹 Pruned overrides (no longer needed)
apify@4.0.0-beta.12>@crawlee/core|types|utilspins to4.0.0-beta.25— confirmed no-op: the Sitemap Extractor's ownpackages/actor-scraper/sitemap-scraper/package.jsonalready pins these three exactly to4.0.0-beta.25(plus its own package-leveloverrides), so the workspace-level override forced nothing the direct pin didn't already lock (verified by removing it and re-resolving: only the override's own lockfile entries disappeared, every package resolution unchanged).(
js-yaml: ^5.0.0was re-audited and kept — removing it letscosmiconfig@9.0.2's own nested copy drop to4.3.2, a different major than the rest of the tree; not currently vulnerable, but the override is still doing real work, so it stays.)🚩 Flagged — needs review
undici7.29.0→7.30.1(high/medium/low across 11 advisories) — CAPPED bynx@23.3.2, which pinsundicito the exact version7.29.0; fix requires bumpingnx23.3.2→24.0.6(semver-major, declares7.30.1).nxis pulled in transitively vialerna@10.1.1→@nx/devkit@23.3.2, not a direct dep we can bump in isolation. No tracking Renovate PR currently open. (alert #331, #332, #333, #334, #339, #340, #393, #397, #399, #401, #402)minimatch9.0.9/10.2.5/10.2.6→11.0.1(medium) — CAPPED by multiple independent consumers:@crawlee/core@3.18.2declares^9.0.0;@crawlee/core@4.0.0-beta.25declares^10.0.1;nx@23.3.2/@nx/devkit@23.3.2/lerna@10.1.1each pin it to an exact10.2.5/10.2.6. No single in-range action clears every pinned copy — thenx/lernamajors above are the fix for thenx-pinned copies, and@crawlee/corewould need its own range bumped upstream. No tracking Renovate PR currently open. (alert #405)stream-json1.9.1→3.6.0(medium) — CAPPED by@crawlee/core@4.0.0-beta.25, exact-pinned by the Sitemap Extractor's intentional crawlee-v4-beta stack. A patchedstream-jsonships from much later crawlee v4 betas, but moving offbeta.25is a deliberate, reviewed migration of that whole pinned pre-release stack, not an in-range resolve. → tracked by chore(deps): update sitemap crawlee v4 beta stack #354. (alert #321, #371, #372)basic-ftp5.3.1→6.2.4(medium) — new alert. CAPPED byget-uri@6.0.5(declares^5.0.2), pulled in viapac-proxy-agent@7.2.0→proxy-agent@6.5.0→apify-client@2.26.0.get-uri's own latest,8.0.1, still declares^5.3.1— the fix needs either a new override (forcingbasic-ftpabove whatget-urihas validated against) or an upstreamget-uri/proxy-agentrange bump; not applying a speculative override here. No tracking Renovate PR currently open. (alert #406)🤖 Generated with Claude Code