Add CHANGELOG entry for #4367 - #4368
Merged
Merged
Conversation
The Generate CHANGELOG workflow has not run since 2025-09-08, so the .changelog/4367.txt entry added by #4367 was never folded into CHANGELOG.md. Add it by hand, and restore the "(Unreleased)" header that docs/release-process.md expects to be present when cutting a release.
mgirouard
approved these changes
Sep 25, 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
2 participants
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.
Description
Follow-up to #4367, which fixed bare-string
errors/messagesunmarshalling and added.changelog/4367.txt.That entry will not reach
CHANGELOG.mdon its own. TheGenerate CHANGELOGworkflow runs onpull_request_target, and nopull_request_targetevent has fired in this repo since 2025-09-08 —Generate CHANGELOG,Changelog checkand the milestone bot have all been silent for a year despite being markedactive. The consistency across four workflows suggests the trigger is blocked at the org or repo level rather than anything being wrong with the workflow files.This matches how the last two releases were handled: the 0.117.0 and 0.118.0 entries were written by hand in
docs(changelog):commits, and the.changelog/*.txtfiles from that period (asset-name.txt,content-converter.txt) are still sitting unconsumed in the repo.So this adds the entry
changelog-buildwould have generated, matching the existingBUG FIXES:section format and the.../issues/NNNNlink style the tool emits.It also restores a
## 0.119.0 (Unreleased)header.docs/release-process.mdtells the release cutter to "remove the (Unreleased) portion from the header for the version you are intending to release", but no such header currently exists onv0— so whoever cutsv0.119.0now just sets the date..changelog/4367.txtis intentionally left in place, consistent with the other unconsumed entries, in case the automation is ever restored.Note on the automation
This PR only unblocks the current release. It does not fix the underlying problem that changelog generation and the changelog gate are both inert, which is worth a separate look by someone with repo/org Actions visibility — the
Changelog checkgate silently not running means PRs can merge without a release note and nobody is told.Has your change been tested?
No code change — documentation only. Verified the rendered section matches the surrounding format and that the resulting
CHANGELOG.mddiff is limited to the six added lines.Types of changes
None of the above — documentation only.
Checklist:
No tests apply to a CHANGELOG edit. The last checkbox is not applicable — see #4367 for why that one was left unchecked there.