Skip to content

Update release step of GitHub workflow to use gh CLI#36

Merged
chris-allan merged 1 commit into
glencoesoftware:masterfrom
sbesson:gh_release_updates
Nov 19, 2025
Merged

Update release step of GitHub workflow to use gh CLI#36
chris-allan merged 1 commit into
glencoesoftware:masterfrom
sbesson:gh_release_updates

Conversation

@sbesson
Copy link
Copy Markdown
Member

@sbesson sbesson commented Nov 19, 2025

Inspired by the work in ome/ome-common-java#107, this makes use of the gh CLI available in the GitHub runners with the default GITHUB_TOKEN and the appropriate permissions to create a GitHub release including generated notes and assets instead of a third-party action

@sbesson sbesson requested a review from chris-allan November 19, 2025 09:31
Copy link
Copy Markdown
Member

@chris-allan chris-allan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. We obviously can't really test until we make an actual release but I'm happy for this to go in if you are, @sbesson? We can mop up any idiosyncrasies when we do the next release.

@sbesson
Copy link
Copy Markdown
Member Author

sbesson commented Nov 19, 2025

Agreed that testing these is usually painful. I have created a rc tag on my fork based off this commit which seems to achieve what we need - https://github.com/sbesson/omero-ms-thumbnail/releases/tag/v0.6.1-rc1

@chris-allan
Copy link
Copy Markdown
Member

Looks good.

@chris-allan chris-allan merged commit 842f89d into glencoesoftware:master Nov 19, 2025
5 checks passed
@sbesson sbesson deleted the gh_release_updates branch February 1, 2026 10:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants