ci(publish): publish on pre-releases + add manual dispatch#17
Open
Shivanshu-07 wants to merge 1 commit into
Open
ci(publish): publish on pre-releases + add manual dispatch#17Shivanshu-07 wants to merge 1 commit into
Shivanshu-07 wants to merge 1 commit into
Conversation
The Publish workflow only listened for release 'released' events, which GitHub does not fire for pre-releases (it fires 'prereleased'). As a result the v1.0.5-beta.0 pre-release did not publish to Maven Central. - Add 'prereleased' so beta/pre-releases publish too. - Add workflow_dispatch so a release can be published manually from the Actions tab without (re)creating a GitHub release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
pranavz28
approved these changes
Jun 24, 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
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.
Publish on pre-releases + manual dispatch
.github/workflows/publish.ymlonly triggered onrelease: types: [released]. GitHub firesreleasedonly for non-pre-releases; a pre-release firesprereleased. So whenv1.0.5-beta.0was published as a pre-release, the workflow never ran and nothing reached Maven Central (io.percy:espresso-javastill tops out at1.0.3).Change
prereleased— beta/pre-releases now publish too, while staying correctly flagged as pre-releases on GitHub.workflow_dispatch— lets us publish manually from Actions → Publish → Run workflow without (re)creating a release.Publishing the already-cut
v1.0.5-beta.0after this mergesThe version
1.0.5-beta.0is already onmainand thev1.0.5-beta.0release/tag already exists — no version bump or new release PR needed. Because release/dispatch workflows always use the workflow file from the default branch, merge this first, then either:main(simplest), orv1.0.5-beta.0pre-release to re-emitprereleased.Builds on JDK 11 + the Gradle 7.5 wrapper (compatible; unrelated to the Java-21 dependency-submission CI failure).
🤖 Generated with Claude Code