Bump Holochain to 0.5.6

[lucksus]

Summary by CodeRabbit

• Chores
  • Updated Holochain-related dependencies to version 0.5.6, aligning with the latest compatible branch.
  • Incorporates upstream fixes and minor improvements for improved stability and compatibility.
  • No functional changes or user-visible behavior adjustments expected.

[coderabbitai]

Walkthrough

Updated rust-executor/Cargo.toml to bump three Holochain-related dependencies (holochain, holochain_cli_bundle, holochain_types) from 0.5.5 to 0.5.6 and switch their git branches from 0.5.5-coasys to 0.5.6-coasys. No code or feature flags changed.

Changes

Cohort / File(s)	Summary
Dependency version bumps rust-executor/Cargo.toml	Bumped holochain, holochain_cli_bundle, and holochain_types from 0.5.5 → 0.5.6 and branches 0.5.5-coasys → 0.5.6-coasys; no other edits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update to HC 0.5.3-rc0 #612 — Similar Cargo.toml bumps for the same Holochain dependencies and branches.
• Upgrade Holochain to 0.5.4 #615 — Updates the identical dependency set and branch pointers in rust-executor/Cargo.toml.
• Upgrade Holochain to 0.5.5 #618 — Performs the same Holochain dependency upgrades on the coasys branches.

Poem

I nudge my deps, hop—tick, tock,
From 5.5 to 5.6 we rock.
Branches bloom in coasys spring,
No code to tweak, yet versions sing.
A bunny wink, a cargo cheer—
Fresh carrots, stable gear! 🥕✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch hc-0.5.6

---

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: 0

🧹 Nitpick comments (1)

rust-executor/Cargo.toml (1)

98-100: Pin git dependencies to a commit for reproducible builds.

Branch heads can move; add rev (or a tagged git ref) to lock exact sources. Optional, but recommended for RCs/releases.

Apply after replacing placeholders with the 0.5.6-coasys commit SHA:

- holochain = { version = "0.5.6", features = ["test_utils", "default", "backend-go-pion"], git = "https://github.com/coasys/holochain.git", branch = "0.5.6-coasys" }
+ holochain = { version = "0.5.6", features = ["test_utils", "default", "backend-go-pion"], git = "https://github.com/coasys/holochain.git", rev = "<commit-sha-0.5.6-coasys>" }
- holochain_cli_bundle = { version = "0.5.6", git = "https://github.com/coasys/holochain.git", branch = "0.5.6-coasys" }
+ holochain_cli_bundle = { version = "0.5.6", git = "https://github.com/coasys/holochain.git", rev = "<commit-sha-0.5.6-coasys>" }
- holochain_types = { version = "0.5.6", git = "https://github.com/coasys/holochain.git", branch = "0.5.6-coasys" }
+ holochain_types = { version = "0.5.6", git = "https://github.com/coasys/holochain.git", rev = "<commit-sha-0.5.6-coasys>" }

📜 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 b8407e4 and 4a863ce.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• rust-executor/Cargo.toml (1 hunks)

🔇 Additional comments (3)

rust-executor/Cargo.toml (3)

98-100: Bump looks good and aligns the trio on 0.5.6.

No obvious manifest issues; versions and branches are consistent across holochain, holochain_cli_bundle, and holochain_types.

---

98-100: If CI targets multiple OSes, verify “backend-go-pion” builds everywhere.

That feature can add platform build deps; make sure Linux/macOS/Windows CI jobs are green before merging.

---

98-100: Run local sanity checks to prevent mixed Holochain sources
Execute locally:

cargo metadata --format-version 1 | jq -r '.packages[] | select(.name=="holochain" or .name=="holochain_types" or .name=="holochain_cli_bundle") | "\(.name)\t\(.source)"'
cargo tree -d | rg -nP '^(holo(chain|chain_types|chain_zome_types)|holo_hash)\b'
cargo tree -e features -p holochain

Ensure all three crates resolve to the same git revision and that the enabled holochain features match those declared in Cargo.toml.