ci(publish): manual dry run that cannot upload - #443
Merged
Merged
Conversation
workflow_dispatch runs the same release job (JDK, signing validation, full build and signing) but ends in publishToMavenLocal and is never given the Maven Central credentials. The real publish step now runs only on tag pushes. Lets a release branch prove the publish pipeline before the tag exists; until now the workflow was only ever exercised by the tag push itself.
Merged
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.
Same change as SKaiNET#1294, prompted by the engine 0.56.0 release whose first publish failed in a runner setup step that ordinary CI never exercises.
workflow_dispatch: a manually started run executes the same job — JDK, signing validation, full release build and signing — but ends in./gradlew publishToMavenLocalon the runner. It gets the signing secrets and is never givenmavenCentralUsername/Password, so it cannot upload.Publish to MavenCentralnow hasif: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/').actionlintclean. The dry run cannot be started from this PR (GitHub only offersworkflow_dispatchonce the trigger is on the default branch); first use: the 0.56.0 release branch, before its tag.