Skip to content

chore(deps): security + in-range lockfile refresh - #398

Open
apify-deps[bot] wants to merge 1 commit into
masterfrom
chore/deps-sweep
Open

apify-deps[bot] wants to merge 1 commit into
masterfrom
chore/deps-sweep

Conversation

@apify-deps

@apify-deps apify-deps Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

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.0
  • broad pnpm update -r lockfile 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 routine caniuse-lite/electron-to-chromium/tldts churn)

🧹 Pruned overrides (no longer needed)

  • apify@4.0.0-beta.12>@crawlee/core|types|utils pins to 4.0.0-beta.25 — confirmed no-op: the Sitemap Extractor's own packages/actor-scraper/sitemap-scraper/package.json already pins these three exactly to 4.0.0-beta.25 (plus its own package-level overrides), 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.0 was re-audited and kept — removing it lets cosmiconfig@9.0.2's own nested copy drop to 4.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

  • undici 7.29.0 → 7.30.1 (high/medium/low across 11 advisories) — CAPPED by nx@23.3.2, which pins undici to the exact version 7.29.0; fix requires bumping nx 23.3.2 → 24.0.6 (semver-major, declares 7.30.1). nx is pulled in transitively via lerna@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)
  • minimatch 9.0.9/10.2.5/10.2.6 → 11.0.1 (medium) — CAPPED by multiple independent consumers: @crawlee/core@3.18.2 declares ^9.0.0; @crawlee/core@4.0.0-beta.25 declares ^10.0.1; nx@23.3.2/@nx/devkit@23.3.2/lerna@10.1.1 each pin it to an exact 10.2.5/10.2.6. No single in-range action clears every pinned copy — the nx/lerna majors above are the fix for the nx-pinned copies, and @crawlee/core would need its own range bumped upstream. No tracking Renovate PR currently open. (alert #405)
  • stream-json 1.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 patched stream-json ships from much later crawlee v4 betas, but moving off beta.25 is 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-ftp 5.3.1 → 6.2.4 (medium) — new alert. CAPPED by get-uri@6.0.5 (declares ^5.0.2), pulled in via pac-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 (forcing basic-ftp above what get-uri has validated against) or an upstream get-uri/proxy-agent range bump; not applying a speculative override here. No tracking Renovate PR currently open. (alert #406)

🤖 Generated with Claude Code

@apify-deps apify-deps Bot added the adhoc Ad-hoc unplanned task added during the sprint. label Nov 11, 2026
@coderabbitai

coderabbitai Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Central YAML; Path: .coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: c2645407-a4ff-48f1-a4c3-a959baf3af25

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@apify-deps
apify-deps Bot force-pushed the chore/deps-sweep branch 2 times, most recently from c310b59 to 84b83c4 Compare November 13, 2026 00:25
@apify-deps

apify-deps Bot commented Nov 13, 2026

Copy link
Copy Markdown
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

apify-deps Bot commented Nov 16, 2026

Copy link
Copy Markdown
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).

@apify-deps
apify-deps Bot requested review from B4nan and removed request for B4nan November 16, 2026 00:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants