Skip to content

ci: crew release workflow — prebuilt binaries on crew-v* tags#8

Open
dropdevrahul wants to merge 1 commit into
mainfrom
crew-release-workflow
Open

ci: crew release workflow — prebuilt binaries on crew-v* tags#8
dropdevrahul wants to merge 1 commit into
mainfrom
crew-release-workflow

Conversation

@dropdevrahul

Copy link
Copy Markdown
Owner

There's no release/prebuilt binary for the crew TUI today — it's source-only, and the existing release.yml builds the Python plugin (vX.Y.Z), not the Rust binary.

This adds .github/workflows/crew-release.yml: on a crew-v* tag (or manual dispatch) it cross-compiles crew for macOS arm64/x86_64 and Linux x86_64, then publishes crew-<tag>-<target>.tar.gz (+ .sha256) to a GitHub Release with generated notes.

Separate crew-v* tag namespace so it never collides with the plugin's vX.Y.Z tags. YAML + cargo build --release --locked verified locally.

To cut the first release: git tag crew-v0.1.0 && git push origin crew-v0.1.0.

Cross-compiles the crew TUI for macOS arm64/x86_64 and Linux x86_64 and
attaches crew-<tag>-<target>.tar.gz (+ sha256) to a GitHub Release when a
crew-v* tag is pushed (or via workflow_dispatch). Separate tag namespace so it
doesn't collide with the plugin's vX.Y.Z releases.
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