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

Release shardtree version 0.6 #127

Merged
merged 3 commits into from
Jan 29, 2025
Merged

Release shardtree version 0.6 #127

merged 3 commits into from
Jan 29, 2025

Conversation

nuttycom
Copy link
Contributor

No description provided.

@nuttycom nuttycom force-pushed the release/shardtree-0.6 branch from 03ec3d3 to 3b21d21 Compare January 28, 2025 19:23
@nuttycom nuttycom force-pushed the release/shardtree-0.6 branch from 3b21d21 to 04280c4 Compare January 28, 2025 19:29
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

Copy link
Contributor

@str4d str4d left a comment

Choose a reason for hiding this comment

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

utACK 04280c4 with nit

@@ -18,7 +18,7 @@ categories = ["algorithms", "data-structures"]

[workspace.dependencies]
# Intra-workspace dependencies
incrementalmerkletree = { version = "0.8", path = "incrementalmerkletree" }
incrementalmerkletree = { version = "0.8.1", path = "incrementalmerkletree" }
Copy link
Contributor

Choose a reason for hiding this comment

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

As noted in my other comment, I don't think this is actually necessary; cargo will consider 0.8.0 and 0.8.1 as compatible, and if you're not in a no-std environment then 0.8.1 contains nothing that you need (so this is just an overconstraint).

If, by contrast, the being-published shardtree depended on a new API exposed by incrementalmerkletree then this would be the correct way to express the dependency.

@nuttycom nuttycom merged commit 7ceefde into main Jan 29, 2025
21 checks passed
@nuttycom nuttycom deleted the release/shardtree-0.6 branch January 29, 2025 00:49
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.

3 participants