[lockfile-maintenance]

Update selected lockfiles with a minimum release age of 3 days.

The package managers' native exceptions still apply. Validate updates with the repository's PR CI.

Version changes

Versions are grouped by package name. — means the package was not present.

package-lock.json

Package	Before	After	Change	History
undici	6.28.1	6.29.0	minor	Release history

undici — 6.28.1 → 6.29.0 (1 release)

Back to version changes · Compare · Releases

v6.29.0

What's Changed

• [v6.x] fix(retry): settle exposed body on terminal failure by @​mcollina in [v6.x] fix(retry): settle exposed body on terminal failure nodejs/undici#5778
• Backport upgrade diagnostics lifecycle fixes to v6.x by @​BridgeAR in Backport upgrade diagnostics lifecycle fixes to v6.x nodejs/undici#5833
• test: synchronize the issue-3356 body timeout by @​BridgeAR in test: synchronize the issue-3356 body timeout nodejs/undici#5834

Full Changelog: nodejs/undici@v6.28.1...v6.29.0

Rebase

• Rebase this PR by regenerating lockfiles from the latest base branch.

Check the box above or post a new PR comment with /lockfile rebase on its own line. Requires repository write access.

Workflow requirements and manual fallback

Enable App-based rebase handling with rebase: true in .github/lockfile-maintenance-auth.yml, or configure an Actions request handler as described below.

For Actions-based handling, the workflow must subscribe to pull_request_target: types: [edited] for the checkbox and issue_comment: types: [created] for comments, and configure the request-rebase job.
If these handlers are not configured, open the maintenance workflow and select Run workflow on the branch used for maintenance. This requires workflow_dispatch.

[mergify]

Queued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-10 13:53 UTC · Rule: dependency-updates · triggered by merge protections
• ✅ Checks passed · on draft merge queue: checking #2 + #3 + #4 + #7 together on main (a88e533) #11
• ✅ Merged — 2026-10-10 14:06 UTC · at 76d9689e53ab3d841be606c5b0aa8d2e40f6dd96 · merge-batch via merge queue: checking #2 + #3 + #4 + #7 together on main (a88e533) #11

This pull request spent 12 minutes 52 seconds in the queue, including 1 minute 44 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1
  • Update dependency @yarnpkg/cli-dist to v4.18.1 #2
  • Update dependency ignore to v7.0.12 #3
  • Lockfile maintenance #4
  • Update ruby/setup-ruby action to v1.327.0 #7
• #changes-requested-reviews-by = 0
  • Update dependency @yarnpkg/cli-dist to v4.18.1 #2
  • Update dependency ignore to v7.0.12 #3
  • Lockfile maintenance #4
  • Update ruby/setup-ruby action to v1.327.0 #7
• #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule CI and pull requests]
  • Update dependency @yarnpkg/cli-dist to v4.18.1 #2
  • Update dependency ignore to v7.0.12 #3
  • Lockfile maintenance #4
  • Update ruby/setup-ruby action to v1.327.0 #7
• check-success = test
• github-review-approved [🛡 GitHub repository ruleset rule CI and pull requests]
  • Update dependency @yarnpkg/cli-dist to v4.18.1 #2
  • Update dependency ignore to v7.0.12 #3
  • Lockfile maintenance #4
  • Update ruby/setup-ruby action to v1.327.0 #7
• any of [🛡 GitHub repository ruleset rule CI and pull requests]:
  • check-success = @github-actions/test
  • check-neutral = @github-actions/test
  • check-skipped = @github-actions/test