Repository navigation
chore(deps): dependency sweep - #861
Open
apify-deps[bot] wants to merge 2 commits into
Open
apify-deps[bot] wants to merge 2 commits into
apify-deps[bot] wants to merge 2 commits into
Conversation
![apify-deps[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
Broad in-range refresh (ws 8.22.1 -> 8.22.2 + transitive churn). No security alert required a code/manifest change this run; all 5 open Dependabot alerts were dismissed as not applicable (see PR body).
github-actions
Bot
added
the
t-tooling
…build 1.176.1 (pulled in as a peer by the broad refresh) fails the docs build: "Module not found: Can't resolve 'lodash/kebabCase'". Pinned back via an override until upstream fixes it.
|
See more at https://github.com/apify/apify-sdk-js/actions/runs/42935110514#summary-130243126678 |
This branch has not been deployed
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 only this run (no alert needed a code/manifest change):
ws8.22.1 → 8.22.2 (+ transitive lockfile churn from the broadpnpm update -rrefresh)✅ Dismissed (don't apply to our usage)
decode-uri-component(high) —query-string's only consumer here,@apify/ui-library'sgetVideoSrc(used by the website's markdown renderer), callsstringifyUrl()with a fixed YouTube/Vimeo embed URL that never has a pre-existing query string, sodecode-uri-component's vulnerable decode path is never exercised with attacker input. (alert #284)decode-uri-component(medium) — same path as chore: try to fix the puppeteer download in CI #284. (alert #274)tinypool(critical) — pulled solely by@docusaurus/core(website build tooling, pinned^1.0.2). Upstream closed this exact advisory as not applicable for the same usage in Security: Update to Tinypool 2.1.2 in @docusaurus/[email protected] - CVE-2026-104848 CVE-2026-104849 meta/docusaurus#12584. (alert #281)tinypool(critical) — same transitive as test: fix e2e tests #281. (alert #280)basic-ftp(high) —get-uri's FTP parser only runs viaproxy-agent'spac+*scheme proxies (verified inproxy-agent's source:pac-proxy-agentis only selected forpac+data/pac+file/pac+ftp/pac+http/pac+httpsproxy URLs). Nothing inapify/crawlee/apify-clientever constructs apac+proxy URL — only an operator manually setting an exotic PAC-script proxy env var could reach it. (alert #279)Notes
webpack-dev-server: ^6.0.0override inpnpm-workspace.yaml: still needed —@docusaurus/coredeclares^5.2.2, and dropping the override would reopen previously-fixed alerts (docs: fix the edit this page link #244, chore(deps): update actions/checkout digest to 8ade135 #229) on the 5.x line. Kept as-is.@apify/ui-librarypeer 1.176.0 → 1.176.1, which broke the docs build (Module not found: Can't resolve 'lodash/kebabCase'). Added'@apify/ui-library': 1.176.0tooverridesto hold it back; drop this override once a fixed upstream version is available.@apify-packages/*dependency in this repo, so the CATCH UP step is a no-op.🤖 Generated with Claude Code