CI: really include ChangeLog via gh rel edit - #51
Open
knocte wants to merge 5 commits into
Open
Conversation
Since the tag was manually pushed, GitHub automatically created
a lightweight release/tag placeholder on GitHub because of the
pushed tag (or because of some automatic UI
configuration/behavior). When gh release create
"${{ env.HEAD_TAG }}" ran, GitHub might have replied "Release
already exists" (or did not overwrite the existing
notes/placeholder because it was already created with the
default commit message "chore: release v0.0.755").
To fix this and make it extremely reliable: if the release
already exists (or gh release create fails or skips because
it's already there), we fallback to gh release edit with:
````
gh release edit "${{ env.HEAD_TAG }}" --notes-file CHANGELOG_RELEASE.md
````
This guarantees that even if a placeholder is pre-created by
GitHub because of the pushed tag, we overwrite and update its
release notes with our newly generated conventional changelog
block! Updated publish.yml to support this create || edit
fallback.
I did small manual tweaks to release notes after tagging, so let's make them match to this .md file.
knocte
force-pushed
the
wip/fixReleaseJobToIncludeChangeLog
branch
from
May 28, 2026 01:20
0c9d658 to
e0a2160
Compare
knocte
force-pushed
the
wip/fixReleaseJobToIncludeChangeLog
branch
from
May 28, 2026 04:17
e0a2160 to
81bc02b
Compare
knocte
force-pushed
the
wip/fixReleaseJobToIncludeChangeLog
branch
from
May 28, 2026 07:09
22d2ed6 to
a26177f
Compare
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
1 participant
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.
Since the tag was manually pushed, GitHub automatically created a lightweight release/tag placeholder on GitHub because of the pushed tag (or because of some automatic UI
configuration/behavior). When
gh release create "${{ env.HEAD_TAG }}"ran, GitHub might have replied "Release already exists" (or did not overwrite the existing notes/placeholder because it was already created with the default commit message "chore: release v0.0.755").To fix this and make it extremely reliable: if the release already exists (or gh release create fails or skips because it's already there), we fallback to gh release edit with:
This guarantees that even if a placeholder is pre-created by GitHub because of the pushed tag, we overwrite and update its release notes with our newly generated conventional changelog block! Updated publish.yml to support this create || edit fallback.