fix: update undici to 8.10.0 to resolve CVE-2026-13697 and 4 related CVEs - #42
Open
independabot-soc2[bot] wants to merge 1 commit into
Open
fix: update undici to 8.10.0 to resolve CVE-2026-13697 and 4 related CVEs#42independabot-soc2[bot] wants to merge 1 commit into
independabot-soc2[bot] wants to merge 1 commit into
Conversation
Co-Authored-By: Oz <oz-agent@warp.dev>
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.
Hi, this is independabot — not Lili! You can ask her if you have questions, but she had no hand in generating this PR other than setting up the independabot schedule.
Please merge this PR yourself, if you approve.
BEFORE YOU MERGE
Instructions for resolving the vuln — test to make sure that nothing is broken, check compatibility, etc.
undiciis a transitive runtime dependency (@actions/http-client@4.0.1→undici). The repo already pinned it via anoverridesentry, but the floor (>=6.27.0) resolved to the vulnerable8.5.0. Dependabot could not fix this itself (update_not_possible). Raised the override floor to>=8.9.0; the lock now resolvesundici@8.10.0.dist/index.js+ sourcemap were regenerated vianpm run package, as required byAGENTS.md.undici8.5.0 → 8.10.0 (viaoverrides.undici>=6.27.0→>=8.9.0)=in Cache-Controltypenpm audit— no remainingundicifinding (npm ls undici→undici@8.10.0)npm run package— bundle rebuilt successfullynpm run lint— cleannpm run format:check— cleannpm test(vitest) — 27/27 passingHighlight the risky code / where the dependency was used
undiciis never imported directly by this repo. It only reaches us through@actions/http-client, which is used bysrc/index.tsfor the Oz API calls, and by@actions/tool-cachefor downloading theozpackage. Both paths are exercised by plain HTTP GET/POST, so the cache/cookie/retry-interceptor behavior changes in 8.9.0/8.10.0 are unlikely to affect us — but the download-and-install path is the thing worth smoke-testing.Note that
undici@8.xrequiresnode >= 22.19.0; this action targetsnode24and.node-versionis24.4.0, so this is unchanged from the pre-existing8.5.0resolution.Special instructions for this PR
dist/index.jsanddist/index.js.mapare checked-in build artifacts, so the diff is large. They were produced solely bynpm run packageon top of the dependency bump — no hand edits..github/workflows/test_e2e.yaml) to confirm theozinstall + agent run path still works with the rebuilt bundle.npm auditstill reports unrelatedajv,brace-expansion, andyamlfindings. Those have no open Dependabot alerts and are intentionally left out of scope here.AFTER YOU MERGE
No post-merge steps.
Conversation: https://staging.warp.dev/conversation/d2bfa0fb-0e2b-4ff5-906d-5a97e4439614
Run: https://oz.staging.warp.dev/runs/019fd203-b4c4-726c-a82f-9308f3ae9a66
This PR was generated with Oz.