Releases are driven by cargo-dist.
Pushing a v* tag triggers .github/workflows/release.yml, which builds
binaries for every target listed in dist-workspace.toml, uploads them to
a GitHub Release, updates the Homebrew tap, and finally pushes the four
crates to crates.io.
-
Create the Homebrew tap repo on GitHub:
julymetodiev/homebrew-veles— empty, public, default branchmain. No files needed; cargo-dist will populate it. -
Add repository secrets at
https://github.com/julymetodiev/Veles/settings/secrets/actions:Secret Source Used for CARGO_REGISTRY_TOKENcrates.io → Account → API Tokens, scope publish-updatepublish-cratesworkflowHOMEBREW_TAP_TOKENGitHub → Settings → Developer settings → PAT (fine-grained), scope Contents: Read and writeonhomebrew-velescargo-dist Homebrew job The
HOMEBREW_TAP_TOKENis required because GitHub's defaultGITHUB_TOKENcan only push to the repo it ran in. cargo-dist needs to commit to the tap repo, which is separate. -
Publish each crate manually for the first time (cargo-dist's publish-crates workflow uses
cargo publishagainst an existing crate; the very first publish has to come from a maintainer's local machine):cargo login # paste your crates.io token cargo publish -p veles-core cargo publish -p veles-grpc cargo publish -p veles-mcp cargo publish -p veles-cliAfter this, the workflow handles every subsequent release.
-
Make sure
mainhas everything you want and CI is green. -
Bump the version in
Cargo.toml's[workspace.package]:[workspace.package] version = "0.2.0"
-
Commit:
git add Cargo.toml Cargo.lock git commit -m "release: v0.2.0" -
Tag and push:
git tag v0.2.0 git push origin main git push origin v0.2.0
-
Watch the Release workflow at
https://github.com/julymetodiev/Veles/actions. It runs:plan— validate configbuild-*— one job per target triple (~3-5 min each, parallel)host— collects artifacts, generates checksums + installerspublish-homebrew— pushes the formula update tohomebrew-velespublish-crates— runscargo publishfor the four cratesannounce— creates the GitHub Release page
If
publish-cratesfails (network, propagation timing, name conflict), the GitHub Release and Homebrew formula are still good — you can re-run only that job from the Actions UI.
Tags with a hyphen (v0.2.0-rc.1, v0.2.0-beta, …) are marked as
pre-releases automatically and are not pushed to crates.io / Homebrew by
default. Useful for testing the binaries before a stable cut.
cargo install cargo-dist
dist init --yes # bumps cargo-dist-version + regenerates release.yml
git diff .github/workflows/release.yml dist-workspace.tomlReview the diff, commit, ship.