Repository navigation
build: publish zk-encryption-circuits on crates.io - #8
Merged
Merged
Conversation
The circuit layer takes the workspace version and is published right after zk-encryption, which it re-exports (a semver range, so a consumer resolves one copy of the wallet types).
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.
zk-encryption-circuitsbecomes publishable: workspace version, crates.io metadata,zk-encryptionas a0.1range (one copy of the wallet types for consumers).zk-encryption, thenzk-encryption-circuits, each skipped if its version is already published. It installs libc++, which the circuit crate's barretenberg link needs.cargo publish -p zk-encryption-circuits --dry-runpackages (bundled bytecode, ~1.2 MB) and builds against the publishedzk-encryption 0.1.4. Merging releases v0.1.5 with both crates.