Skip to content

Add binary release workflow - #119

Merged
mveril merged 4 commits into
mainfrom
feature/basic-deployment
Oct 11, 2026
Merged

mveril merged 4 commits into
mainfrom
feature/basic-deployment

Conversation

@mveril

@mveril mveril commented Oct 11, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add a tag-triggered release workflow that checks package versions, builds RustiQ archives for six platform targets, publishes the workspace packages to crates.io, and creates a GitHub Release with SHA-256 checksums.
  • Document release contents, archive verification, installation, and Cargo publishing prerequisites.
  • Update the installation guide with registry and tagged-binary options.

The workflow requires the repository Actions secret CARGO_REGISTRY_TOKEN before tagged releases can publish to crates.io.

Verification

  • mdbook build docs
  • mdbook test docs
  • pytest tools/test_book_links.py
  • python tools/check-book-links.py docs/book --config docs/book.toml
  • git diff --check

@mveril
mveril force-pushed the feature/basic-deployment branch from 497be5d to 3d9fdf7 Compare October 11, 2026 15:48
@mveril
mveril merged commit 6d4f67c into main Oct 11, 2026
17 checks passed
@mveril
mveril deleted the feature/basic-deployment branch October 11, 2026 18:22
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