chore: Update dependencies to latest versions #276
Merged
Conversation
This file contains 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
Upgrade various dependencies across multiple crates to their latest compatible versions
Benchmark for b87ce19Click to view benchmark
|
Benchmark for b87ce19Click to view benchmark
|
…eases Upgrade serde and serde_json dependency versions using more flexible version specifiers
Benchmark for 101da62Click to view benchmark
|
Benchmark for b87ce19Click to view benchmark
|
Benchmark for 101da62Click to view benchmark
|
Benchmark for 101da62Click to view benchmark
|
|
please check this zkmopro/ark-zkey#1 (comment) |
Upgrade Ark and Wasmer dependencies to their latest minor versions, including: - ark-circom from 0.1.0 to 0.5.0 - ark-zkey from 0.1.0 to 0.1.2 - wasmer from 2.3.0 to 2.3.x - num-traits to 0.2.19 Also update Makefile to improve cross-platform build process for wabt
Benchmark for c6c0158Click to view benchmark
|
Benchmark for 6f4bd0aClick to view benchmark
|
Remove ark-zkey optional dependency and update Wasmer to version 4.4.0 across multiple crates. Modify circuit module to include necessary structs and functions previously provided by ark-zkey.
Benchmark for 4af8d2bClick to view benchmark
|
Benchmark for 3dd5515Click to view benchmark
|
Benchmark for 4af8d2bClick to view benchmark
|
Benchmark for 3dd5515Click to view benchmark
|
Benchmark for 4af8d2bClick to view benchmark
|
Benchmark for 3dd5515Click to view benchmark
|
Clean up project structure by removing the rln-wasm package, associated GitHub workflows, and WASM-specific configurations. This includes: - Removing rln-wasm directory and its contents - Updating Cargo.toml workspace configuration - Removing WASM-specific build and test configurations from CI workflows - Removing WASM-related dependencies and features from RLN crate
Benchmark for a3c9d55Click to view benchmark
|
Benchmark for d09290fClick to view benchmark
|
Benchmark for a3c9d55Click to view benchmark
|
Benchmark for b2696c8Click to view benchmark
|
Benchmark for d09290fClick to view benchmark
|
Benchmark for a3c9d55Click to view benchmark
|
Benchmark for b2696c8Click to view benchmark
|
Benchmark for d09290fClick to view benchmark
|
Benchmark for b2696c8Click to view benchmark
|
|
When "make installdeps" and "make test" are executed, which is specified in the main README file, errors occur. No other suspicious things have been found. |
could you provide log for for |
|
UPDATE: The problem with
The part containing warnings and errors: |
Benchmark for ee23aeeClick to view benchmark
|
|
@AlekseiVambol I've fixed problem with |
Benchmark for ee23aeeClick to view benchmark
|
Benchmark for ee23aeeClick to view benchmark
|
Currently, the tests do not produce errors. No other problems have been found. |
AlekseiVambol
approved these changes
Feb 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
UPD: As a result it was decided to deprecate the wasm part, besides here also the makefile is fixed and so far the work with arkzkey is completely inside the code without using the library (todo: consider the option of returning to mopro )
Main problem: zerokit fixes many dependencies and some versions are too old and new libraries don't support them and a conflict happened
the main conflict is around
once_cellandnum_traitsonce_cell- already fixednum_traits- cannot be fixed yet because this strict dependency came fromark-zkey, and there it in turn came from a fork on an old version of arc-circom where version 2.15 is fixedOpen issue in ark-zkey: zkmopro/ark-zkey#1