feat: Add release workflow and config #5209
Merged
Conversation
This file contains 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
Created `.github/workflows/jreleaser.yml` to trigger the next release version. The workflow dispatches on user input for `major`, `minor`, and `patch` versions by setting up the environment using JDK 11, Go, and `semver`. Configuration files such as `.gitignore` and `jreleaser.yml` were also updated to ignore specific files and to set the `MIT` license.
MartinWitt
changed the title
|
@I-Al-Istannen had the brilliant idea to make the release commit on a new branch and if the tests etc. succeed we fast-forward this branch to master. This guards as against failures of tests during the release process. |
I-Al-Istannen
requested changes
May 16, 2023
I-Al-Istannen
approved these changes
May 16, 2023
|
thanks a lot @MartinWitt , we'll try the workflow together next week. |
Closed
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.
This is a jreleaser workflow we already use for maven lockfile. The secrets are set, see
There workflow itself is pretty easy. You have a dropdown menu and decide if you want a patch/minor/major release. JReleaser updates the version and does the release to maven-central and github. If you want some extra feature have a look at https://jreleaser.org/guide/latest/reference/index.html. There are a lot of possibilities.