Repository navigation
⬆️ build(deps): require release-creator 4.3.2 - #38
Merged
gaborbernat merged 1 commit intoOct 30, 2026
Merged
Conversation
release-creator 4.3.2 succeeds when the fragment directory is missing, which failed the 6.2.2 release: every change since 6.2.1 skipped news, so the checkout had no changelog.d.
gaborbernat
added
skip news
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.
The 6.2.2 Prepare release run failed in
release-creator fragmentswithNo such file or directory: 'changelog.d': every change since 6.2.1 carriedskip news, and Git keeps no empty directory. release-creator 4.3.2 treats a missing fragment directory as nothing to link.The release-creator floors rise to
>=4.3.2, and the temporary cooldown override moves to 4.3.2's upload time, still expiring 2026-11-06. Only release-creator moved inpylock.toml.