chore: bump to light-sdk 0.25.0, light-hasher 7.0.0, light-client 0.25.0 - #36
Open
ananas-block wants to merge 2 commits into
Open
chore: bump to light-sdk 0.25.0, light-hasher 7.0.0, light-client 0.25.0#36ananas-block wants to merge 2 commits into
ananas-block wants to merge 2 commits 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: Advanced 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 |
…nt 0.25.0 The light-sdks release is on crates.io, so drop the [patch.crates-io] sections that redirected light-sdk, light-hasher, light-client and light-macros to a light-sdks git commit, and take the published crates. light-sdk 0.24.0 -> 0.25.0 light-hasher 6.0.0 -> 7.0.0 light-client 0.25.0 (requirement unchanged, now resolved from crates.io) light-macros 3.0.0 (requirement unchanged) The release moves the Solana dependencies to the newest versions on the Agave 4.2 line (sysvar 4.1, clock 3.1, message 4.4, transaction-error 3.3, hash 4.5, define-syscall 5.2, spl-token-2022-interface 3.1) and anchor-lang to 1.2.0. Lockfiles are regenerated with cargo update: the locked solana-define-syscall 5.1.0 blocks resolution of the new requirements otherwise. 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.
ananas-block
changed the title
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.
Summary
Move the examples on the 0.24 stack to the light-sdks release published on 2026-09-10, which brings light-client transaction v1 support (Agave 4.2, SIMD-0385) and the Solana dependencies of the Agave 4.2 line.
Two commits:
chore: use light-client 0.25.0 with transaction v1 support: bumped light-client to 0.25.0 while the release was unpublished, redirecting the light crates to a light-sdks git commit via[patch.crates-io].chore: use published light-sdk 0.25.0, light-hasher 7.0.0, light-client 0.25.0: drops the patch sections and takes the published crates.Version bumps
Resolved transitively from crates.io: light-sdk-types 0.25.0, light-sdk-macros 0.25.0, light-account-checks 0.10.0, light-merkle-tree-metadata 0.13.0, light-event 0.25.0, light-prover-client 10.0.0, light-concurrent-merkle-tree 7.0.0, light-indexed-merkle-tree 7.0.0, light-merkle-tree-reference 6.0.0, light-indexed-array 0.5.0, anchor-lang 1.2.0.
Affected workspaces
account-comparison, basic-operations/anchor (burn, close, create, reinit, update), basic-operations/native, counter/anchor, counter/native, create-and-update, read-only, zk/nullifier.
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.
Notes
cargo update. The previously locked solana-define-syscall 5.1.0 blocks resolution of the new requirements otherwise, so downstream projects taking this release need the same step.mainand on this branch: the prover bundled with CLI 0.28.4 fetches a proving-key CHECKSUM file from a bucket path that returns 404.Verification
All twelve affected workspaces pass
cargo check --all-targetsagainst the published crates.