chore: new release v4.6.1-pre.0

[SWvheerden]

Description

New release esme

Summary by CodeRabbit

• New Features

  • Added reporting of readiness status during initialization.

• Bug Fixes

  • Fixed database resizing issue on Jellyfish Merkle Tree (JMT) write operations.
  • Corrected minotari_merge_mining_proxy to avoid returning a Tari block hash when the submit_to_origin flag is disabled.

• Documentation

  • Updated changelogs and README to reflect new version numbers and recent changes.

• Chores

  • Bumped version numbers across multiple packages and configuration files to 4.6.1-pre.0.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update increments version numbers from 4.6.0-pre.0 to 4.6.1-pre.0 (and corresponding release versions) across multiple Cargo.toml files, documentation, and configuration files. Changelog files are updated with entries for version 4.6.1, detailing a new feature and two bug fixes. No changes to code or public entity declarations are present.

Changes

File(s)	Change Summary
Cargo.toml, applications/minotari_ledger_wallet/comms/Cargo.toml, applications/minotari_ledger_wallet/wallet/Cargo.toml, applications/minotari_miner/Cargo.toml, comms/rpc_macros/Cargo.toml, infrastructure/test_utils/Cargo.toml	Version numbers updated from 4.6.0-pre.0 to 4.6.1-pre.0
changelog-Mainnet.md, changelog-development.md, changelog-nextnet.md	Added entries for version 4.6.1, including a new feature and two bug fixes
README.md	Updated recommended binary versions for Mainnet, Nextnet, and Esmeralda to 4.6.1, 4.6.1-rc.0, and 4.6.1-pre.0
supply-chain/config.toml	Updated exemption version strings from 4.6.0-pre.0 to 4.6.1-pre.0 for multiple packages; criteria unchanged

Possibly related PRs

• tari-project/tari#7229: Previous version bump from 4.5.0-pre.0 to 4.5.0-rc.0, updating version strings and exemption entries.
• tari-project/tari#7228: Earlier version increment from 4.4.1-pre.0 to 4.5.0-pre.0, updating version metadata and documentation.

Suggested reviewers

• hansieodendaal

Poem

A hop, a skip, a version bump,
From zero to one, we make the jump!
Changelogs fresh, the docs align,
All the numbers now entwine.
No code was harmed, just numbers spun—
Release 4.6.1, another run!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d21f99c and 4decce3.

⛔ Files ignored due to path filters (4)

• Cargo.lock is excluded by !**/*.lock
• applications/minotari_ledger_wallet/wallet/Cargo.lock is excluded by !**/*.lock
• clients/ffi_client/package-lock.json is excluded by !**/package-lock.json
• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (11)

• Cargo.toml (1 hunks)
• README.md (1 hunks)
• applications/minotari_ledger_wallet/comms/Cargo.toml (1 hunks)
• applications/minotari_ledger_wallet/wallet/Cargo.toml (1 hunks)
• applications/minotari_miner/Cargo.toml (1 hunks)
• changelog-Mainnet.md (1 hunks)
• changelog-development.md (1 hunks)
• changelog-nextnet.md (1 hunks)
• comms/rpc_macros/Cargo.toml (1 hunks)
• infrastructure/test_utils/Cargo.toml (1 hunks)
• supply-chain/config.toml (2 hunks)

---

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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai 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

Documentation and Community

• 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.