Skip to content

chore(deps): dependency sweep - #4107

Open
apify-deps[bot] wants to merge 2 commits into
masterfrom
chore/deps-sweep
Open

chore(deps): dependency sweep#4107
apify-deps[bot] wants to merge 2 commits into
masterfrom
chore/deps-sweep

Conversation

@apify-deps

@apify-deps apify-deps Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Dependency sweep — in-range freshening (no security bumps landed via this PR — see below):

  • Broad pnpm update -r across the workspace: patch/minor bumps only (e.g. @apify/* packages, tar7.5.22, puppeteer/playwright patch lines, zod catalog ^4.4.3^4.5.4, etc).
  • Narrowed one piece of that refresh after CI feedback: oxlint / @oxlint/plugins / @apify/oxlint-config moved to their latest in-range versions initially, but the newer oxlint enables stricter rules that flag pre-existing code patterns (no functional change here) — reverted to their prior exact versions (oxlint/@oxlint/plugins 1.62.0, @apify/oxlint-config 0.2.5) to keep Lint green, per the sweep runbook's "narrow rather than ship red CI" guidance. That rule fallout can be addressed as its own follow-up whenever the team wants to take the newer oxlint.

🧹 Pruned overrides (no longer needed)

  • minimatch (top-level ^9.0.0) — stale: it was capping @crawlee/core's own direct dependency (declared ^10.0.1) down to 9.x. Dropped; @crawlee/core now resolves its own minimatch to ^10.2.6 as declared. The lerna-scoped lerna>minimatch: ^3.1.4 override (needed for lerna 9.x's v3-only bundled code) is untouched and still does its job.

✅ Dismissed (don't apply to our usage)

  • stream-json (medium, GHSA-528h-pc64-c93x) — not_used: the advisory is specific to the pick/ignore/filter/replace path filters (O(D²) on nesting depth). Crawlee's only usage (packages/core/src/serialization.ts) is the StreamArray streamer, which the advisory itself lists as not affected (asm.depth, O(1)). No filter API is used anywhere in the repo. Patched 3.5.0 is also a major bump outside the declared ^1.9.1 range, so a version bump isn't an option here anyway — this is a clean not-applicable dismissal. (alert #692)

🤖 Generated with Claude Code

Broad in-range freshening across the pnpm workspace (patch/minor bumps
only, ranges unchanged) plus dropping the top-level `minimatch: ^9.0.0`
override in pnpm-workspace.yaml: it was capping @crawlee/core's own
`^10.0.1` dependency down to 9.x even though core's declared range
already wants v10. The lerna-scoped override (`lerna>minimatch: ^3.1.4`)
still handles lerna's v3-only bundled code, so this is untouched.
@apify-deps apify-deps Bot added the adhoc Ad-hoc unplanned task added during the sprint. label Sep 7, 2026
@apify-deps
apify-deps Bot requested a review from B4nan September 7, 2026 01:35
The broad in-range freshening picked up oxlint 1.62.0 -> 1.81.0 (and
@oxlint/plugins, @apify/oxlint-config in lockstep) since it's still
within the declared ^1.62.0 caret range, but the newer oxlint enables
stricter lint rules that flag pre-existing code patterns across many
files, turning a green Lint CI check red without any real behavior
change here. Master's Lint is green on the old version, so per the
dependency-sweep runbook: narrow the refresh rather than ship red CI.
Exact-pinning oxlint/@oxlint/plugins/@apify/oxlint-config back to their
prior locked versions until that rule fallout is addressed separately.
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.

2 participants