Repository navigation
fix(changelog): format Docker Undici security fragment for release integrity - #18259
Merged
diegosouzapw merged 1 commit intoOct 27, 2026
Conversation
Closed
4 tasks
diegosouzapw
merged commit Oct 27, 2026
97abc57
into
cheaper-inference:release/v3.8.53
0 of 36 checks passed
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.
Problem
The latest official
release/v3.8.53commit866c46dintroducedchangelog.d/fixes/0000-docker-undici-security-floor.mdas plain prose, without a leading Markdown bullet. The officialcheck:changelog-integrityvalidator requires every fragment to begin with-, and its Quality GatesMerge integrity (changelog + generated skills)step fails on this fragment. Confirmed on our clean upstream-merge hosted CI run 40380015110.Fix
Change only this single fragment line to begin
- **fix(docker):**, retaining the original Undici 6.29.1 security-floor description unchanged. No runtime code, dependencies, lockfiles, or API behavior changed.This is upstream-generic (not an Oscar/Order Forge fork customization). Once merged, downstream forks can absorb it through normal upstream sync instead of carrying a permanent custom patch.