fix build releases created via GitHub UI - #192
Merged
jenspapenhagen merged 6 commits intoSep 7, 2026
Merged
Conversation
Releases created via the GitHub web UI create the tag server-side without a push event, so the `on: push: tags: ['v*']` trigger never fired and no build/assets were produced (e.g. v2.0.3). - Add `release: types: [published]` trigger (fires for every UI-published release) - Derive version from the release event or the triggering tag - Replace softprops/action-gh-release with gh CLI that tolerates an already existing release (create-if-missing + upload --clobber) - Guard Maven publish / README / badge steps against the self-triggered duplicate run (release created by this workflow itself)
jenspapenhagen
changed the title
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.
release: types: [published]trigger — fires for every published release, including UI-created onesgithub.event.release.tag_name || github.ref_name(works for both the tag-push and the release event)ghCLI: creates the release only if it does not exist yet, always uploads assets with--clobber. The old action would fail with 422 on an already existing (UI-created) release.publishedevent fires again and would double-publish to Maven Central. A newskip_duplicatestep detects releases authored bygithub-actions[bot]and skips publish/README/badge steps on that run (build is retained as validation, run stays green).