chore: new release v1.13.2-pre.0

[SWvheerden]

Description

new release esmeralda

Summary by CodeRabbit

• Chores

  • Updated version numbers across packages and documentation.
  • Revised network version recommendations for improved consistency.

• New Features

  • Enhanced scripting support for safer and smoother transaction processing.
  • Improved wallet functionality, including better handling of one-sided transactions and auto-update features.
  • Introduced support for zero-confirmation transactions and refined network protocol separation.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request primarily updates version numbers from 1.13.1-pre.0 to 1.13.2-pre.0 across multiple Cargo.toml files and related configuration files. In addition, the README has been updated with new recommended network versions for Nextnet and Esmeralda. The changelog documents detailed modifications for a new TariScript feature and other blockchain-related enhancements including transaction data structures, metadata commitment signatures, network separation, and wallet transaction improvements.

Changes

File(s)	Change Summary
Cargo.toml (workspace), applications/minotari_ledger_wallet/{comms, wallet}/Cargo.toml, applications/minotari_miner/Cargo.toml, base_layer/contacts/src/chat_client/Cargo.toml, comms/rpc_macros/Cargo.toml, infrastructure/test_utils/Cargo.toml	Updated package version from "1.13.1-pre.0" to "1.13.2-pre.0".
README.md	Updated recommended network versions: Nextnet from 1.13.0-rc.0 to 1.13.2-rc.0 and Esmeralda from 1.13.0-pre.0 to 1.13.2-pre.0.
supply-chain/config.toml	Updated exemption versions from "1.13.1-pre.0" to "1.13.2-pre.0" for multiple dependencies (e.g., minotari_miner, tari_comms_rpc_macros, tari_wallet, etc.).
changelog-development.md	Introduced TariScript feature enhancements including new transaction data structures (ComSig), metadata commitment signatures, gamma calculation fixes, additional block header fields, network separation, zero-confirmation transactions, auto-update functionality, and improved wallet handling of one-sided transactions.

Sequence Diagram(s)

sequenceDiagram
    participant Wallet
    participant TariScriptEngine
    participant BaseNode
    participant Miner

    Wallet->>TariScriptEngine: Submit transaction with TariScript details
    TariScriptEngine->>Wallet: Request commitment signature (ComSig)
    Wallet->>TariScriptEngine: Provide ComSig & transaction data
    TariScriptEngine->>BaseNode: Validate transaction & calculate gamma
    BaseNode->>Miner: Forward validated transaction
    Miner-->>BaseNode: Confirm inclusion in block
    BaseNode-->>Wallet: Transaction confirmed & updated

Loading

Possibly related PRs

• chore: new release v1.11.7-pre.0 #6847: Involves similar version number updates in Cargo.toml files for various packages.
• chore: new release v1.11.4-pre.0 #6800: Updates Cargo.toml version numbers from a previous pre-release series, indicating a parallel modification pattern.

Poem

I'm a rabbit with a hop so light,
Updates in versions, crisp and right.
Cargo files, configs in tune,
TariScript sings a brand new tune.
Leaping through code with joy today,
Pre-release changes pave the way!
🐰✨

---

📜 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 8f43ff5 and f0ef26b.

⛔ Files ignored due to path filters (2)

• Cargo.lock is excluded by !**/*.lock
• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (10)

• 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)
• base_layer/contacts/src/chat_client/Cargo.toml (1 hunks)
• changelog-development.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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.