Uh oh!
There was an error while loading. Please reload this page.
chore: bump transitive @xmldom/xmldom to resolve dependabot alert - #162
Conversation
Lockfile-only bump of @xmldom/xmldom 0.8.14 -> 0.8.15 (transitive dep of release-please@17.11.2 in the private release-please-ai package). Resolves Dependabot alert #11 (GHSA-6gmq-8vp8-gcm6 / CVE-2026-83610, medium, vulnerable >=0.7.0 <=0.8.14, first patched 0.8.15). Change-Id: I715341073f469245f25f73bdf2163f95760012db Signed-off-by: Thomas Kosiewski <tk@coder.com>
ThomasK33
commented
Sep 3, 2026
@codex review |
ThomasK33
commented
Sep 3, 2026
@codex security review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Codex Review: Didn't find any major issues. 🎉 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Security review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
Lockfile-only bump of the transitive dependency
@xmldom/xmldomfrom 0.8.14 → 0.8.15 to resolve Dependabot alert #11. Dependabot's own update job failed on pnpm, hence the manual fix.Alert
EntityReference.nodeNameduringrequireWellFormedserialization>= 0.7.0, <= 0.8.14pnpm-lock.yamlDependency chain
packages/release-please-ai(private, unpublished) →release-please@17.11.2→@xmldom/xmldom(declared range^0.8.4)@xmldom/xmldomis not in the dependency graph of any published package (@coder/ai-sdk-agent,@coder/ai-sdk-provider,@coder/ai-sdk-sandbox); it is only reachable through the private release tooling.What changed
Only
pnpm-lock.yaml, viapnpm update -r @xmldom/xmldom(release-please's declared range^0.8.4already admits 0.8.15, so nooverridesentry was needed and nopackage.jsonmanifest was touched):packagesentry@xmldom/xmldom@0.8.14→@xmldom/xmldom@0.8.15(new integrity hash verified againstnpm view @xmldom/xmldom@0.8.15 dist.integrity; thedeprecated:marker on 0.8.14 goes away)snapshotsentry@xmldom/xmldom@0.8.14→@xmldom/xmldom@0.8.15release-please@17.11.2snapshot dependency'@xmldom/xmldom': 0.8.14→0.8.15Nothing else in the lockfile changed (+4/−5 lines). No
@xmldom/xmldomversion<= 0.8.14remains anywhere in the lockfile.Validation
All via
mise exec --on the pushed head:pnpm install --frozen-lockfile✅pnpm check(oxfmt + oxlint + typecheck) ✅pnpm -r build✅pnpm -r test✅ (provider 22, release-please-ai 13, agent 326, effect 45, sandbox 191 tests passed)pnpm publint✅pnpm attw✅Live e2e intentionally skipped: this is a lockfile-only change to a transitive dependency of the private release tooling; no published package's runtime or the Coder transport code path is affected.
Generated with
mux• Model:anthropic:claude-fable-5-1• Thinking:xhigh