Add GitHub release creation to Maven workflow#107
Merged
melissalinkert merged 3 commits intoome:masterfrom Nov 5, 2025
Merged
Conversation
Member
Author
|
As these workflows are notoriously hard to test, see https://github.com/sbesson/ome-common-java/releases/tag/v6.1.1-rc1 for an example of GitHub release created on my fork from a tag at commit e43af6e. |
Member
melissalinkert
left a comment
There was a problem hiding this comment.
Worth adding permissions in the build step as in ome/ome-model#224?
melissalinkert
approved these changes
Nov 5, 2025
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.
In preparation of the next patch release of
ome-common-java. As we moved away from manually maintained change log files in favour of GitHub releases with generated notes (#97), this automates the creation of the latter using theghCLI