chore(deps): dependency sweep — website lockfile freshening - #1050
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1050 +/- ##
==========================================
+ Coverage 87.34% 95.24% +7.89%
==========================================
Files 59 59
Lines 5509 5509
==========================================
+ Hits 4812 5247 +435
+ Misses 697 262 -435
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
apify-deps
Bot
force-pushed
the
chore/deps-sweep
branch
from
September 7, 2026 12:14
3fc45a6 to
d4e0b0f
Compare
B4nan
approved these changes
Sep 7, 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 of
website/pnpm-lock.yaml(@apify/ui-library1.164.8 → 1.164.9,oxlint^1.80.0 → ^1.81.0, plus a few new@types/*transitives; no other declared ranges changed).✅ Dismissed (don't apply to our usage)
qs(medium) — tolerable_risk: pulled only viawebpack-dev-server → express → body-parser, used exclusively by localpnpm start(dev server), never invoked in CI (CI only runsdocusaurus build). No fix available in theexpress/body-parser4.x line (declared range~6.15.1excludes the patched6.16.0; no newer 4.x release exists). (alert #159)qs(medium) — same rationale as above (array-limit bypass variant). (alert #160)🚩 Flagged — needs review
decode-uri-component0.4.1→0.5.0(medium) — new override needed. Pulled viaquery-string@8.2.0(still latest 8.x, declares^0.4.1) →@apify/ui-library@1.164.9(latest, still declares^8.1.0forquery-string) →@apify/docs-theme's search modal, which runs client-side in the deployed docs site (real runtime path, not dev-only). No in-range fix exists:decode-uri-component@0.5.0needs a new pnpm override (query-string's declared range excludes it), or aquery-stringmajor bump to9.x(which itself violates@apify/ui-library's declared^8.1.0range). No tracking PR found. (alert #158)🤖 Generated with Claude Code