ethereum / ethereum/sonobe

release: publish to crates.io?

Open
#186 2 comments 0 reactions 0 assignees View on GitHub
chore/release
Dominant language
Rust
Stars
285
Forks
97
PR merge metrics
No merged PRs in 30d

Description

It seems like it wouldn't take too much work to publish most of these crates to crates.io.

There's some odd exceptions for certain github based dependencies:
- `noname`
- `ark-circom`
Are the main ones I'd worry about. I believe `acvm` could be taken from crates.io as well (though it would be worth communicating with Noirlang team.

Easiest move forward would be to feature gate: `noname` and `circom`

Then could publish without those features and add in later as needed and update `default-features` too.

Thoughts?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by auditing the crates and their dependencies, focusing on the GitHub-based noname and ark-circom dependencies and the availability of acvm on crates.io. Done means the publishable crates and dependency exceptions are agreed, feature gating and default-features behavior are defined, and the crates can be published with the Noirlang communication considered.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.