chore: use light-client 0.25.0 with transaction v1 support - #36
Open
ananas-block wants to merge 1 commit into
Open
chore: use light-client 0.25.0 with transaction v1 support#36ananas-block wants to merge 1 commit into
ananas-block wants to merge 1 commit into
Conversation
Bump light-client from 0.24.0 to 0.25.0 in the examples on the 0.24 stack. The release is not published yet, so each workspace root redirects the light-* crates it uses (light-sdk, light-hasher, light-macros, light-client) to the same Lightprotocol/light-sdks commit via [patch.crates-io], the setup the repo used before the switch to published crates. Pinning every light-* crate to one source keeps a single copy of each in the dependency graph. light-client 0.25.0 moves the Solana RPC stack from 4.0.0-rc.0 to 4.2 and adds transaction v1 (SIMD-0385) support. No source changes were needed. Untouched: simple-claim, counter/pinocchio and zk-id stay on the 0.23 stack because they depend on light-protocol crates that are not in light-sdks. All twelve affected workspaces pass cargo check --all-targets. The counter/native validator test fails identically on main and on this branch: the prover bundled with CLI 0.28.4 fetches a CHECKSUM file for proving keys from a bucket path that now returns 404. Drop the patch sections once light-client 0.25.0 is on crates.io.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Bump light-client from 0.24.0 to 0.25.0 in the examples on the 0.24 stack. The release is not published yet, so each workspace root redirects the light-* crates it uses (light-sdk, light-hasher, light-macros, light-client) to the same Lightprotocol/light-sdks commit via [patch.crates-io], the setup the repo used before the switch to published crates. Pinning every light-* crate to one source keeps a single copy of each in the dependency graph.
light-client 0.25.0 moves the Solana RPC stack from 4.0.0-rc.0 to 4.2 and adds transaction v1 (SIMD-0385) support. No source changes were needed.
Untouched: simple-claim, counter/pinocchio and zk-id stay on the 0.23 stack because they depend on light-protocol crates that are not in light-sdks.
All twelve affected workspaces pass cargo check --all-targets. The counter/native validator test fails identically on main and on this branch: the prover bundled with CLI 0.28.4 fetches a CHECKSUM file for proving keys from a bucket path that now returns 404.
Drop the patch sections once light-client 0.25.0 is on crates.io.