Skip to content

chore: release#32

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-plz-2026-07-06T14-42-21Z
Open

chore: release#32
github-actions[bot] wants to merge 1 commit into
mainfrom
release-plz-2026-07-06T14-42-21Z

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

Review the Release PR

  • Version bumps match user-visible changes for each crate (major for network upgrades or breaking API, minor for new API/behavior/RPC/config, patch otherwise)
  • Each changed crate's [Unreleased] entries follow the Changelog Guidelines (operator-focused in the root CHANGELOG.md, crate-consumer-focused per crate)
  • [Unreleased] has been renamed to the release heading (## [Zebra <version>] in the root, ## [<version>] per crate)
  • No git dependencies remain in crates publishing to crates.io (check-no-git-dependencies)
  • Any required checkpoint, end-of-support height, README, or operational changes already landed
  • RELEASE_APP_ID and RELEASE_APP_PRIVATE_KEY are configured at repository or organization scope
  • Merge only when crates should publish and the public zebrad GitHub Release should be created

Release Summary

  • zebra-chain: 11.0.0 -> 11.0.1
  • tower-batch-control: 1.0.1 -> 1.1.0
  • zebra-network: 10.0.0 -> 10.0.1
  • zebrad: 6.0.0-rc.0 -> 6.0.0-rc.1
  • zebra-node-services: 9.0.0 -> 9.0.1
  • zebra-script: 10.0.0 -> 10.0.1
  • zebra-state: 10.0.0 -> 10.0.1
  • zebra-consensus: 10.0.0 -> 10.0.1
  • zebra-rpc: 11.0.0 -> 11.0.1
  • zebra-utils: 9.0.0 -> 9.0.1

This PR was generated with release-plz.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants