Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependencies #808

Merged
merged 7 commits into from
Apr 11, 2023
Merged

Update dependencies #808

merged 7 commits into from
Apr 11, 2023

Conversation

str4d
Copy link
Contributor

@str4d str4d commented Apr 11, 2023

No description provided.

@str4d str4d added this to the Release 5.5.0 milestone Apr 11, 2023
Copy link
Contributor

@nuttycom nuttycom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK with nonblocking suggestion

@@ -21,4 +21,3 @@ codegen-units = 1
[patch.crates-io]
zcash_encoding = { path = "components/zcash_encoding" }
zcash_note_encryption = { path = "components/zcash_note_encryption" }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we get rid of the path-based dependencies here? IIRC right now we're depending upon the released versions of these crates in zcash_primitives and the other crates.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I remove that, we end up compiling zcash_note_encryption twice: once for the copy in the workspace, and once for the released version (both of which end up in Cargo.lock). It looks like only the released version gets used as a dependency, so maybe it's fine? In any case, changing this is sort of out-of-scope for this PR, because patch dependencies are only used in the local workspace; they don't affect downstream crate users.

@str4d str4d changed the title Migrate to orchard 0.4 and fpe 0.6 Update dependencies Apr 11, 2023
@@ -15,7 +15,7 @@ categories = ["cryptography::cryptocurrencies", "encoding"]
keywords = ["zcash", "address", "sapling", "unified"]

[dependencies]
bech32 = "0.8"
bech32 = "0.9"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AFAICT this dependency is not exposed, so we can cut a point release of zcash_address at the same time we cut zcash_primitives 0.11 et al.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is automatically generated, right?

Copy link
Contributor Author

@str4d str4d Apr 11, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes; it is generated if protoc is present in the path and the protobuf files are present. We don't include the protobuf files in the published releases (so that downstream users aren't forced into a hard dependency on protoc), instead checking in the generated output.

Copy link
Contributor

@nuttycom nuttycom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re-utACK f82866d

Copy link
Contributor

@daira daira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@str4d str4d merged commit f2f9903 into main Apr 11, 2023
@str4d str4d deleted the orchard-0.4 branch April 11, 2023 18:25
@str4d str4d mentioned this pull request Mar 12, 2024
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.

4 participants