[pull] master from apify:master - #269
Merged
Merged
Conversation
## Summary Dependency sweep — security bumps + in-range freshening (all within existing ranges): - `@hono/node-server` → 1.19.17, `hono` → 4.13.3 (medium/low, multiple alerts) - `fast-uri` → 3.1.5 (high, multiple alerts) - `dompurify` → 3.4.13 (medium/low, multiple alerts) - `js-yaml` → 3.15.1 / 4.3.1 (high, multiple alerts) - `nx` → 22.7.8 (medium, multiple alerts) - `mermaid` → 11.16.1 (medium/low, multiple alerts) - `ip-address` → 10.5.0, via an in-range `express-rate-limit` 8.3.2 → 8.6.2 bump (high/medium, multiple alerts) - `undici` → 7.29.0 (medium/high/low, multiple alerts) - `postcss` → 8.5.26 (medium/high, multiple alerts) - `svgo` → 3.3.4 (high) - `markdown-it` → 14.3.0, `linkify-it` → 5.0.2 (medium/high, multiple alerts) - `body-parser` → 1.20.6 (low) - `axios` → 1.18.1 / 1.19.0 (medium/high, multiple alerts) - `protobufjs` → 7.6.5 (medium/high, multiple alerts) - `webpack-dev-server` → 5.2.6 (medium, multiple alerts) - `shell-quote` → 1.10.0 (critical/high) - `brace-expansion` → 1.1.18 / 2.1.4 (high, multiple alerts) - `websocket-driver` → 0.7.5 (critical/medium) - `sigstore` → 4.1.1, `@sigstore/core` → 3.2.1, `@sigstore/verify` → 3.1.1 (high/medium) - `http-proxy-middleware` → 2.0.10 (medium) - `joi` → 17.13.4 (medium) - `launch-editor` → 2.14.1 (medium) - `@babel/core` → 7.29.7 (low) - `ws` → 7.5.13 (high) - `turbo` → 2.9.14+ range bump (medium) - `qs` → 6.15.3 (medium, one occurrence — see flagged for the other) - `uuid` → 11.1.1 for the reachable 11.x line (medium) - plus opportunistic in-range minor freshening across the rest of `pnpm-lock.yaml` ## ✅ Dismissed (don't apply to our usage) - `uuid` (medium) — `not_used`: the only remaining pre-11.1.1 copies are `sockjs`'s `8.3.2` (webpack-dev-server, dev-only) and `@langchain/core`'s `10.0.0` (stagehand e2e devDependency), both of which only ever call `v4()`. The advisory is about missing bounds-checks in `v3()`/`v5()`/`v6()` when a caller supplies a custom output buffer — a path neither consumer exercises. The reachable 11.x copy is bumped to the patched `11.1.1` in this PR. ([alert #571](https://github.com/apify/crawlee/security/dependabot/571)) - `serialize-javascript` (medium) — `not_used`: pulled only by `copy-webpack-plugin` and `css-minimizer-webpack-plugin`, which are webpack plugins. The docs build uses Docusaurus's rspack bundler (`future.faster.rspackBundler: true`), so the webpack path never runs and the vulnerable serialize step isn't executed. ([alert #572](https://github.com/apify/crawlee/security/dependabot/572)) ## 🚩 Flagged — needs review - `vite` `8.0.8` → `8.0.16` (medium/high) — peer-only dependency of `vitest@4.1.4` (not a direct devDependency anywhere in the repo), so `pnpm update`/overrides can't move it in-range; reaching the patch means pinning `vite` as a direct devDependency, a manifest change outside this sweep's scope. ([alert #591](https://github.com/apify/crawlee/security/dependabot/591), [alert #593](https://github.com/apify/crawlee/security/dependabot/593)) - `esbuild` `0.27.7` → `0.28.1` (low) — pinned by `css-minimizer-webpack-plugin`'s docusaurus/webpack toolchain and by the same peer-pinned `vite@8.0.8` above; no existing override to bump. ([alert #588](https://github.com/apify/crawlee/security/dependabot/588)) - `qs` `6.14.2` → `6.15.2` (medium) — pinned by `express@4.22.1`'s exact `~6.14.0` range (used by the docs `webpack-dev-server` chain); needs a new `pnpm-workspace.yaml` override to force past `6.14.x`. ([alert #573](https://github.com/apify/crawlee/security/dependabot/573)) No open Renovate PR references any of `vite`, `esbuild`, or `qs` at the moment. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: apify-deps[bot] <4649591+apify-deps[bot]@users.noreply.github.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )