[4.2] Simplify the release process #2745
Draft
+25
−253
Conversation
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
marko-bekhta
commented
Nov 7, 2025
| ) | ||
|
|
||
| // See https://docs.asciidoctor.org/gradle-plugin/latest/common-task-configuration/#choosing-an-execution-mode-for-asciidoctorj | ||
| executionMode = org.ysb33r.grolifant.api.core.jvm.ExecutionMode.JAVA_EXEC |
Member
Author
There was a problem hiding this comment.
this one is a bonus 😄
we don't really need it for releases or anything ... but it helps with asciidoc building 🙂
Member
|
Nice, thanks. |
This was referenced Nov 12, 2025
DavideD
changed the title
This was referenced Nov 12, 2025
marko-bekhta
force-pushed
the
build/release-update
branch
from
4250acd to
b88e1dd
Compare
marko-bekhta
commented
Nov 13, 2025
Comment on lines
+1
to
+3
|
|
||
| * See the [website](https://hibernate.org/reactive/releases/{{releaseVersionFamily}}) for requirements and compatibilities. | ||
| * See the [What's New](https://hibernate.org/reactive/releases/{{releaseVersionFamily}}/#whats-new) guide for details about new features and capabilities. |
Member
Author
There was a problem hiding this comment.
The idea is that each project/branch can add something extra about a particular release if it wants to.
This template is then included in the reactive template https://github.com/hibernate/hibernate-release-scripts/blob/b5852b88067e9b71fd746a69917a2b92576ce7f1/jreleaser/github-release-note-template/reactive.tpl
but if you'd want something different for your github releases we can discuss that 🙂
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.
Hey Davide 🙂 👋🏻
I'm opening this as a draft for now. We'll need to merge the scripts update first.
the idea behind this iteration of release updates is .... project builds should only build the artifacts (e.g. jars/javadocs/html docs etc) and put them in the specific location. Then the release scripts would do the rest.
This means that the project build does not need to do any git operations or deployments or ... 😃