Skip to content

task (release): Add workflow to publish binaries for each platform.#446

Closed
jafin wants to merge 1 commit intombrt:masterfrom
jafin:task/publish-binaries
Closed

task (release): Add workflow to publish binaries for each platform.#446
jafin wants to merge 1 commit intombrt:masterfrom
jafin:task/publish-binaries

Conversation

@jafin
Copy link
Copy Markdown
Contributor

@jafin jafin commented Feb 15, 2026

Amend to your preference.

Summary

  • Add GitHub Actions workflow to build and publish release binaries for multiple platforms
  • Supports manual trigger (workflow_dispatch) and automatic trigger on version tags

Changes

Introduces a new release workflow (.github/workflows/release.yml) that automates the creation of platform-specific binaries when a new version is released.

Relates to #427

Copy link
Copy Markdown
Owner

@mbrt mbrt left a comment

Choose a reason for hiding this comment

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

I think it would be easier to rework the whole workflow and make it end to end. Perhaps using gorelease and merging with .github/workflows/bump-version.yml.

- name: Determine version
id: version
run: |
if [ "${{ github.event_name }}" = "workflow_dispatch" ] && [ -n "${{ inputs.tag }}" ]; then
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

I think it's safer to use git describe --always --tags --dirty for all cases instead of manually constructing this?

- name: Determine version
id: version
run: |
if [ "${{ github.event_name }}" = "workflow_dispatch" ] && [ -n "${{ inputs.tag }}" ]; then
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Why is this duplicated?

@github-actions
Copy link
Copy Markdown
Contributor

This pull request is stale because it has been open for 30 days without activity.
This will be closed in 7 days, unless you add the 'lifecycle/keep-alive' label or comment.

@github-actions github-actions Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity, has become stale and will be auto-closed. label Mar 20, 2026
@jafin jafin closed this Mar 20, 2026
@gene1wood
Copy link
Copy Markdown

I think it would be easier to rework the whole workflow and make it end to end. Perhaps using gorelease and merging with .github/workflows/bump-version.yml.

I've done so in #450

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/stale Denotes an issue or PR has remained open with no activity, has become stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants