chore(deps): npm: bump undici from 7.28.0 to 7.29.0

[dependabot]

Bumps undici from 7.28.0 to 7.29.0.

Release notes

Sourced from undici's releases.

v7.29.0

⚠️ Security fixes

High severity

• GHSA-4cwx-7wf7-3272: malformed qualified private Cache-Control directives could cause cross-user information disclosure in shared caches or a parse-time crash. The cache parser now treats empty qualified directives conservatively and safely handles mixed qualified and unqualified directives. Fixed by 9f10f1e9, with regression coverage in 466e99d1.

Medium severity

• GHSA-m8rv-5g2x-5cg5: a malicious type property on a duck-typed blob-like HTTP/1.1 request body could inject CRLF sequences into the generated content-type header. Undici now coerces and validates the value before adding it to the request. Fixed by 33928bc2.
• GHSA-jr45-8vmc-qm54: optional whitespace around = in qualified no-cache and private directives could bypass shared-cache restrictions and disclose authenticated data across users. Cache-Control parsing now normalizes these forms and applies conservative cache decisions. Fixed by 98011a86.
• GHSA-8xcm-r25x-g524: the retry interceptor could expose a stale Content-Length after resuming a partial response, potentially causing downstream response desynchronization, hangs, or corruption. Undici now rejects partial responses whose Content-Length is inconsistent with Content-Range. Fixed by 1b5a5312, with corrected fixtures in 4a9dafb1.
• GHSA-v3r7-h72x-cjcm: unsanitized domain and unparsed values passed to setCookie() could inject cookie attributes. Undici now validates cookie domains, paths, and unparsed attributes more strictly. Fixed by 3bf91ddb.

Full Changelog: nodejs/undici@v7.28.0...v7.29.0

Commits

• 9e38fc1 Bumped v7.29.0 (#5590)
• d887e34 fix: validate coerced header values for CRLF (#5579)
• 33928bc fix: validate blob body content type
• 98011a8 fix(cache): harden cache directive parsing
• 4a9dafb test(retry): correct broken content-range fixtures in retry-handler.js
• 1b5a531 fix(retry): reject partial content length mismatch
• 466e99d test: cover crash on mixed unqualified and qualified private cache directives
• 9f10f1e fix: handle empty qualified private cache directive
• 3bf91dd fix: harden cookie domain, path, and unparsed attribute validation
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[scottschreckengaust]

Principal Architect Review — PR #708 (chore(deps): npm: bump undici 7.28.0 → 7.29.0)

1. Verdict

Approve. Correct, minimal, automated transitive-dependency security bump that strictly reduces the repo's vulnerability surface. Zero blocking issues. The one red CI check is not attributable to this diff (see Tests & CI).

2. Vision alignment

Advances the tenet of a reliable, bounded control plane: undici 7.29.0 patches four advisories — GHSA-4cwx-7wf7-3272 (High, CVSS 7.4, cross-user info disclosure via malformed private Cache-Control directives), GHSA-jr45-8vmc-qm54 (shared-cache bypass), GHSA-m8rv-5g2x-5cg5 (CRLF injection in content-type), and GHSA-v3r7-h72x-cjcm (cookie-attribute injection). Keeping HTTP-client dependencies patched directly serves control-plane security. No tenet is traded; no ADR required.

3. Blocking issues

None.

4. Non-blocking suggestions / nits

1. Second copy of vulnerable undici still present — integrations/jira-forge-app/package-lock.json still pins undici@7.28.0 and carries the identical four GHSAs (confirmed in the failing osv-scanner output). This is out of scope for this yarn.lock-only PR and is already covered by the npm ecosystem directories: ["**/*"] block in .github/dependabot.yml (open-PR limit 1, so it is queued behind this one). No action needed here; just ensure the sibling Dependabot PR is merged promptly to clear the advisory.
2. Governance (informational, waived) — Per ADR-003 the gate is an approved backing issue. This is an automated Dependabot security bump with no backing issue and a bot branch name (dependabot/npm_and_yarn/undici-7.29.0); consistent with prior merged deps PRs (e.g. #624, #625), this is a de-facto waiver for automated maintenance, not a blocker.

5. Documentation

No docs required — no behavior, contract, env var, command, or public-API change. A transitive lockfile bump has no user-facing surface. Starlight mirror unaffected. No drift.

6. Tests & CI

No tests required or possible for a lockfile version bump; the dependency's own test suite covers the fix.

CI status: build (agentcore) pass, Validate PR title pass, Dead-code detection pass, CodeQL/auto-approve skipped. Secrets, deps, and workflow scan is RED — but the failure is pre-existing and NOT caused by this PR. The osv-scanner run reports 11 findings across sibling lockfiles: fast-uri 3.1.4 and ip-address 10.2.0 (yarn.lock), cryptography 49.0.0 (agent/uv.lock), and the forge-app undici 7.28.0 copy (nit #1). This PR removes undici from the yarn.lock findings — it is a strict net improvement. Blocking a security patch on unrelated queued Dependabot items would be counterproductive; recommend landing the sibling bumps (fast-uri, ip-address, cryptography, forge-app undici) to return the branch to green. No CDK construct/stack change → bootstrap synth-coverage not applicable.

7. Review agents run

The diff is a 3-line change to a single generated lockfile (yarn.lock) — no hand-authored source, types, control flow, comments, or tests. I hand-verified the only reviewable dimension: version, integrity (sha512), and resolved URL are mutually consistent and undici@^7.19.0 (transitive via cheerio) is satisfied by 7.29.0; corroborated the security rationale against the release notes and the osv-scanner CI output. Agents omitted, each because the diff genuinely does not touch its scope:

• code-reviewer — omitted: no hand-authored source/style surface (generated lockfile only).
• silent-failure-hunter — omitted: no error-handling or fallback code.
• type-design-analyzer — omitted: no new/changed types.
• comment-analyzer — omitted: no comments in the diff.
• pr-test-analyzer — omitted: no test files and none warranted for a version bump.
• /security-review — omitted as a code review: no IAM/Cedar/network/secrets/input-gateway code touched. The security dimension here is the dependency advisory itself, which I assessed directly above.

8. Human heuristics

• Proportionality — Pass. Single-line-triple lockfile edit; no abstraction or scope creep.
• Coherence — Pass. Belongs in root yarn.lock; matches the established Dependabot flow and commit convention.
• Clarity — Pass. Commit message and PR body state the CVEs and rationale precisely.
• Appropriateness — Pass. Automated, reversible, maintainable; the fix is validated by undici's own regression tests referenced in the release notes.

[dependabot]

Looks like undici is up-to-date now, so this is no longer needed.