ci: auto-publish Rust crates to crates.io on release#272
Merged
DorianZheng merged 1 commit intomainfrom Feb 16, 2026
Merged
Conversation
Add `publish_crates` job to build-runtime workflow that publishes boxlite and its dependency crates to crates.io after runtime tarballs are uploaded to the GitHub Release. - Publish leaf crates first (boxlite-shared, *-sys), wait 60s for crates.io indexing, then publish boxlite - Use BOXLITE_DEPS_STUB=1 to skip native builds during verification - boxlite uses --no-verify (shim binary links libkrun, unavailable in stub mode; real build already succeeded) - Handle "already uploaded" gracefully for idempotent re-runs - Add publish=false to boxlite-ffi (path-only dep would fail publish) - Document CARGO_REGISTRY_TOKEN secret in workflows README
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
publish_cratesjob tobuild-runtime.ymlthat publishes Rust crates to crates.io after runtime tarballs are uploaded to GitHub Releasepublish = falsetoboxlite-ffi(path-only dep would fail publish)CARGO_REGISTRY_TOKENsecret in workflows READMEPre-requisite
Create
CARGO_REGISTRY_TOKENsecret in repo settings (generate at https://crates.io/settings/tokens with publish-new + publish-update scopes).Test plan
actionlintpasses on workflow YAMLBOXLITE_DEPS_STUB=1 cargo publish --dry-runpasses for all 6 cratescargo package --listconfirms vendor dirs excluded, proto files included