chore: bump batched merkle tree v0.3.0 -> v0.4.0

[ananas-block]

Summary by CodeRabbit

• Chores
  • Upgraded several core libraries across the workspace to their latest versions.
  • Improves overall stability, compatibility, and performance with newer dependencies.
  • No changes to user-facing features or behavior.
  • No configuration or feature flag updates required.
  • Internal package versions aligned for consistency and easier maintenance.

[coderabbitai]

Walkthrough

Bumps versions of Light workspace crates in root Cargo.toml and updates corresponding crate versions in program-libs manifests: compressed-account (0.3.0→0.4.0), zero-copy (0.2.0→0.3.0), zero-copy-derive (0.1.0→0.3.0), and batched-merkle-tree (0.3.0→0.4.1). No feature, path, or API changes.

Changes

Cohort / File(s)	Summary of Changes
Workspace dependency versions Cargo.toml	Updated dependency versions: light-compressed-account 0.3.0→0.4.0, light-zero-copy 0.2.0→0.3.0, light-zero-copy-derive 0.1.0→0.3.0, light-batched-merkle-tree 0.3.0→0.4.1.
Program libs crate versions program-libs/batched-merkle-tree/Cargo.toml, program-libs/compressed-account/Cargo.toml, program-libs/zero-copy-derive/Cargo.toml, program-libs/zero-copy/Cargo.toml	Bumped crate package versions to match: batched-merkle-tree 0.3.0→0.4.1, compressed-account 0.3.0→0.4.0, zero-copy-derive 0.1.0→0.3.0, zero-copy 0.2.0→0.3.0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore: bump rust crate versions #1812 — Similar Cargo.toml version bumps for the same Light crates across the workspace.
• refactor: sdk tests #1911 — Adjusts workspace usage of light-zero-copy and reorganizes SDK test members; overlaps in crate-level manifest dependencies.

Suggested reviewers

• sergeytimoshin
• SwenSchaeferjohann

Poem

I nudge the tags, hop-hop—now new,
Versions bloom like morning dew.
No code to twist, no logic maze,
Just tidy crates in numbered arrays.
Thump of joy, my changelog beat—
Carrots counted, updates neat. 🥕✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch jorrit/chore-bump-batched-merkle-tree-version-0-4-0

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 96c2faa and fe26a35.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (5)

• Cargo.toml (2 hunks)
• program-libs/batched-merkle-tree/Cargo.toml (1 hunks)
• program-libs/compressed-account/Cargo.toml (1 hunks)
• program-libs/zero-copy-derive/Cargo.toml (1 hunks)
• program-libs/zero-copy/Cargo.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)

• GitHub Check: stateless-js-v1
• GitHub Check: lint
• GitHub Check: Test program-libs-fast
• GitHub Check: Test batched-merkle-tree-simulate
• GitHub Check: Test sdk-libs
• GitHub Check: Test program-libs-slow
• GitHub Check: cli-v2
• GitHub Check: Test concurrent-merkle-tree
• GitHub Check: Forester e2e test
• GitHub Check: cli-v1
• GitHub Check: stateless-js-v2

🔇 Additional comments (6)

program-libs/zero-copy-derive/Cargo.toml (1)

3-3: Version bump to 0.3.0 looks good.
Matches workspace dependency updates; no feature or dep drift here.

program-libs/zero-copy/Cargo.toml (1)

3-3: Version bump to 0.3.0 acknowledged.
Aligns with derive crate; no manifest drift spotted.

program-libs/batched-merkle-tree/Cargo.toml (1)

3-3: Confirm version bump in Cargo.toml matches PR title
PR title references 0.4.0, but Cargo.toml is set to 0.4.1. If 0.4.1 is intended, update the PR title; otherwise revert the version in Cargo.toml:

-version = "0.4.1"
+version = "0.4.0"

program-libs/compressed-account/Cargo.toml (1)

3-3: Version bump to 0.4.0 looks good.
No related feature/dependency changes needed here.

Cargo.toml (2)

162-162: Root workspace dep updated to 0.4.0 (compressed-account) — OK.
Consistent with package manifest.

---

165-166: zero-copy(+derive) to 0.3.0 — OK.
No feature changes; derives remain optional.

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Root dep uses light-batched-merkle-tree 0.4.1 while PR title says 0.4.0.
Please either update the PR title or downgrade here to 0.4.0 for consistency:

-light-batched-merkle-tree = { path = "program-libs/batched-merkle-tree", version = "0.4.1" }
+light-batched-merkle-tree = { path = "program-libs/batched-merkle-tree", version = "0.4.0" }

Additionally, verify the lockfile and repo for stale references:

---

🏁 Script executed:

#!/bin/bash
# Show versions in Cargo.lock (if present)
if [ -f Cargo.lock ]; then
  rg -nC1 -e '^name = "light-(batched-merkle-tree|zero-copy|zero-copy-derive|compressed-account)"' Cargo.lock
fi

# Ensure no leftover 0.3.0 refs for batched merkle tree
rg -n -S 'light-batched-merkle-tree".*0\.3\.0' -g '!**/target/**'

# Summarize current versions in workspace manifests
rg -n -g 'Cargo.toml' -e 'name = "light-(batched-merkle-tree|zero-copy|zero-copy-derive|compressed-account)"|^version = "'

Length of output: 3662

---

Update PR title to 0.4.1
The root Cargo.toml path dep, the program-libs/batched-merkle-tree crate, and Cargo.lock all reference light-batched-merkle-tree v0.4.1; no stale v0.3.0 entries remain.

🤖 Prompt for AI Agents

In Cargo.toml at line 185 update the PR title to match the dependency version
0.4.1; change any repository/PR metadata or branch title used for this change to
read "0.4.1" so it aligns with the referenced dependency
light-batched-merkle-tree = { path = "program-libs/batched-merkle-tree", version
= "0.4.1" and ensure any release/merge descriptions or changelog entries in this
PR also reflect version 0.4.1 for consistency.