Skip to content

feat: publish CLI binaries with releases and add --version - #3

Merged
gmegidish merged 1 commit into
mainfrom
ci/release-binaries
Sep 29, 2026
Merged

gmegidish merged 1 commit into
mainfrom
ci/release-binaries

Conversation

@gmegidish

Copy link
Copy Markdown
Member

Summary

Prepares v1.0.1.

  • Release assets: the release job cross-compiles the CLI and attaches four zips, named as mobilecli's are:

    • appmeta-1.0.1-macos-arm64.zip
    • appmeta-1.0.1-macos-amd64.zip
    • appmeta-1.0.1-linux-arm64.zip
    • appmeta-1.0.1-linux-amd64.zip

    Each holds a single appmeta binary, built with CGO_ENABLED=0, -trimpath and -s -w.

  • appmeta --version: prints appmeta version <version>. The workflow sets it with -ldflags -X main.version; local builds print dev. The flag has no short form.

  • CHANGELOG: adds the 1.0.1 section the release notes are taken from.

Notes for the reviewer

  • All four binaries are built on the one Linux runner. The code is pure Go, so no macOS runner is needed.
  • The macOS binaries are not code-signed or notarized.
  • Unlike mobilecli, nothing is published to npm.

Test plan

  • go vet ./... and go test -race ./...
  • Ran the build step locally with GITHUB_REF_NAME=v1.0.1: four zips produced, and the macOS arm64 binary prints appmeta version 1.0.1
  • CI green on this PR
  • After merge: tag v1.0.1 and confirm the release has the four zips and the changelog notes

A release now attaches the appmeta CLI for macOS and Linux, on arm64 and
amd64, each as appmeta-<version>-<os>-<arch>.zip. The release version is
set in the binary at build time.
@gmegidish
gmegidish merged commit 221f4cc into main Sep 29, 2026
22 checks passed
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.

1 participant