Bump undici from ^6.24.0 to ^6.28.0 - #4084
Open
navntoft wants to merge 1 commit into
Open
Conversation
navntoft
force-pushed
the
navntoft/bump-undici
branch
from
August 12, 2026 10:40
b200aa9 to
54a0846
Compare
navntoft
marked this pull request as ready for review
August 12, 2026 11:50
Contributor
There was a problem hiding this comment.
Warning
- Copilot's review of this pull request may be incomplete because some of the changed files are excluded by your Copilot content exclusion settings. See Excluding content from Copilot for details.
Pull request overview
Updates Undici from 6.24 to 6.28, incorporating upstream bug and security fixes without public API changes.
Changes:
- Raises the Undici dependency and override to
^6.28.0. - Refreshes the lockfile and generated bundle.
Show a summary per file
| File | Description |
|---|---|
package.json |
Updates Undici dependency constraints. |
package-lock.json |
Locks Undici 6.28.0 with matching metadata. |
lib/entry-points.js |
Generated artifact; excluded from review. |
Review details
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Files excluded by content exclusion policy (1)
- lib/entry-points.js
- Files reviewed: 1/3 changed files
- Comments generated: 0
- Review effort level: Balanced
mbg
approved these changes
Aug 12, 2026
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.
Dependabot should have created a PR for this, but currently fails with "Dependabot has taken too long to create an update".
Releases 6.25 through 6.28 are all bugfix-only with no public API changes.
Risk assessment
Which use cases does this change impact?
Workflow types:
dynamicworkflows (Default Setup, Code Quality, ...).Products:
analysis-kinds: code-scanning.analysis-kinds: code-quality.upload-sarifaction.Environments:
github.comand/or GitHub Enterprise Cloud with Data Residency.How did/will you validate this change?
pr-checks).If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist