Repository navigation
chore(deps): dependency sweep - #624
Merged
Merged
Conversation
Node: tough-cookie 6.0.2 -> 6.1.0, es-toolkit 1.53.1 -> 1.53.2. Python: coverage, mypy, mypy-extensions, pytest, pytest-asyncio, ruff dev/docs-group bumps.
barjin
approved these changes
Nov 16, 2026
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 security floor reached a clean in-range fix this run; see flags below):
tough-cookie6.0.2 → 6.1.0 (impit-node)es-toolkit1.53.1 → 1.53.2 (impit-node, transitive)coverage,mypy,mypy-extensions,pytest,pytest-asyncio,ruff— dev/docs-group bumps (impit-python)✅ Dismissed (don't apply to our usage)
soupsieve(high) — not_used: transitive viafuro'sdocsdependency group. Every test job runsuv sync --no-group docs, so this group is never installed there; the one job that does install it (docs.yaml→ Sphinx build) usesactions/setup-pythonwithpython-version: 3.x, which resolves to the newest CPython (≥3.11.5) — so it always gets the already-patchedsoupsieve4.0.1, never the locked2.10copy. (alert #140)soupsieve(medium) — same rationale as above. (alert #139)soupsieve(high) — same rationale as above. (alert #138)🚩 Flagged — needs review
minimatch10.2.6 → 11.0.1 (medium) — CAPPED bytypedoc@0.28.20(its latest published release), which still declaresminimatch: ^10.2.5. No newertypedocexists yet with aminimatch@11dependency, and forcing an override would cross a majortypedocitself hasn't adopted. Dev-only (typedoc/typedoc-plugin-mdn-linksdoc generation), but the docs workflow runs on every PR (including forks) with no path filter, so a malicious PR touching typedoc's include/exclude globs is a plausible (if narrow) reach. No tracking PR found. (alert #137)rustls< 0.23.46 (low) — not actually reached by the automated floor check:Cargo.lockpinsrustlsto agitsource (github.com/apify/rustls, rev2b5779e2…), not a crates.io version, so the registry-based floor comparison silently reportedlocked=(not,in,lockfile). Manually confirmed the pinned rev is apify's fork ofrustlsv0.23.45 (git logon the fork shows noPrepare 0.23.46commit and doesn't contain upstream's fix commits8fa0dc5d…/f04804fa…), so the vulnerable code is still present. Both advisories are client-reachable here:impit/Cargo.tomlbuildsrustlswith a customimpitfeature (features=["impit"]→aws_lc_rs, ring, brotli, zlib), i.e. Brotli certificate decompression is compiled in and impit is an HTTP client that talks to arbitrary/untrusted servers. Fixing this needs a new commit in theapify/rustlsfork that merges upstreamv0.23.46+ on top ofimpit-main, then bumping therev=in this repo'sCargo.toml/Cargo.lock— out of scope for this repo-only sweep. (alert #135)rustls< 0.23.46 (low) — same root cause and same fix as above (Brotli cert-decompression memory-exhaustion advisory). (alert #133)🤖 Generated with Claude Code