Open a draft GitHub release after Maven Central - #8
Merged
Merged
Conversation
The formatter's releases end in a draft GitHub release on the tag, and the plugin's had none: release.yml published to Maven Central only. A second job now runs once the central job is done. It takes the jar that went to Maven Central, handed over by the central job, and JReleaser opens a draft release on the tag with that jar, a checksum file, a signature for each and the commits since the previous tag, the shape of the formatter's releases. Publishing the draft stays a click on GitHub. JReleaser's release command deploys as well, so the github-release profile switches the Maven Central deployer off and the GitHub release on; without the profile the POM does what it did before. Both were rehearsed in dry-run on a copy with a local 2.27.0.2 tag: the Central deployment still verifies the POM and builds the bundle, and the release skips the deployer and would upload the jar, checksums_sha256.txt and their .asc files.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Comment on lines
+91
to
+93
| - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 | ||
| with: | ||
| fetch-depth: 0 |
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
2 participants
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 formatter's releases end in a draft GitHub release on the tag; the plugin's had none, because
release.ymlpublished to Maven Central only.github-release, runs once the central job is done. It takes the jar that went toMaven Central, which the central job now hands over as an artifact, and
mvn -P github-release jreleaser:releaseopens a draft release on the tag with that jar,checksums_sha256.txt, an.ascfor each and the commits since the previous tag, the shape of the formatter's releases.Publishing the draft stays a click on GitHub.
github-releaseprofile switches the MavenCentral deployer off and the GitHub release on. Without the profile the POM does what it did
before.
Rehearsed in dry-run on a copy with a local 2.27.0.2 tag: the Central deployment still verifies the POM
and builds the bundle, and the release skips the deployer, lists the commits since 2.27.0.1 and would
upload the jar, the checksum file and their signatures.
2.27.0.1 already has its draft, made by hand from the jar and
.ascon Maven Central (checked againstthe release key 100481FDAEE94DE9).