Repository navigation
build: publish zk-encryption on crates.io - #6
Merged
Merged
Conversation
The wallet crate takes the workspace version, carries crates.io metadata and is published by a new crates-io release job (skipped when the version is already there). The circuits stay on the CDN.
crates-io and publish (R2, checked against what the CDN serves) run first and in parallel; github-release runs last, only when both succeeded, attaching the assets (handed over as a workflow artifact) with the downloads and the crate in its notes.
tonyvelichko
force-pushed
the
chore/publish-crate
branch
from
October 1, 2026 08:19
3168e65 to
104272c
Compare
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
1 participant
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.
What
zk-encryptionbecomes publishable. It takes the workspace version (it was pinned at0.1.0), gains crates.io metadata (readme, docs.rs link, keywords, category), and the README's stalepq_channelcrate name is fixed. The circuits stay on the CDN;zk-encryption-circuitsremains unpublished.crates-iorunscargo publish -p zk-encryption, skipping a version that is already published.publishbuilds the assets, uploads them to R2 and checks that the CDN serves the same files.github-releaseruns only when both succeed, with the assets attached and the CDN downloads and the crate link in its notes.Before merging
CARGO_REGISTRY_TOKENrepository secret (a crates.io token with publish scope forzk-encryption).After the merge, cog tags
v0.1.4(build:bumps a patch) and CI publisheszk-encryption 0.1.4.Checked
cargo publish -p zk-encryption --dry-runpackages and builds. The crate's source is identical tov0.1.1–v0.1.3.cargo test -p zk-encryption --releasepasses.i.