chore: new release v1.13.1-pre.0

[SWvheerden]

New esme release

Summary by CodeRabbit

• New Features

  • Introduced support for custom transaction scripts and one-sided transactions, enhancing wallet capabilities.
  • Enabled software auto-updates and network separation for improved base node operations.

• Improvements

  • Enhanced transaction validation, error handling, and logging for smoother performance.
  • Refined wallet connectivity and recovery processes.

• Chores

  • Consolidated version updates across multiple components.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates version numbers across multiple Cargo.toml files from "1.13.0-pre.0" to "1.13.1-pre.0" and adjusts configuration exemptions accordingly. Additionally, the changelog documents have been updated to describe new features including Tari Script support, one-sided transactions, enhanced wallet connectivity, improved error handling, and auto-update capabilities.

Changes

File(s)	Change Summary
Cargo.toml (workspace), applications/minotari_ledger_wallet/comms/Cargo.toml, applications/minotari_ledger_wallet/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 version numbers from "1.13.0-pre.0" to "1.13.1-pre.0" without changing other configurations.
supply-chain/config.toml	Updated multiple exemption entries (e.g., for minotari_* and tari_* components) from "1.13.0-pre.0" to "1.13.1-pre.0".
changelog-development.md	Added details on Tari Script support including new transaction data structures, metadata signatures, updated validation protocols, zero-confirmation transactions, and improvements in coinbase transaction handling.
changelog-nextnet.md	Introduced one-sided transaction capability, enhanced wallet connectivity and recovery features, updated Tari Script support, added metadata signature functionality, improved error handling/logging, and implemented auto-update for the base node.

Sequence Diagram(s)

sequenceDiagram
    participant Wallet
    participant TariScriptEngine
    participant BaseNode
    Wallet->>TariScriptEngine: Validate & prepare Tari Script transaction
    TariScriptEngine-->>Wallet: Return validation result
    Wallet->>BaseNode: Submit Tari Script transaction
    BaseNode-->>Wallet: Confirm transaction acceptance

Loading

sequenceDiagram
    participant User
    participant Wallet
    participant ConnectivityService
    participant BaseNode
    User->>Wallet: Initiate one-sided transaction ("make-it-rain")
    Wallet->>ConnectivityService: Request connection to Base Node
    ConnectivityService->>BaseNode: Establish connection
    Wallet->>BaseNode: Transmit transaction details
    BaseNode-->>ConnectivityService: Acknowledge receipt
    ConnectivityService-->>Wallet: Relay confirmation
    Wallet-->>User: Confirm transaction success

Loading

Possibly related PRs

• refactor: move to workspace dependencies #6832: Involves version updates in Cargo.toml files similar to this PR.
• chore: new release v1.11.5-pre.0 #6804: Addresses a version update process in Cargo.toml, albeit with different version increments.

Suggested reviewers

• stringhandler
• hansieodendaal

Poem

I’m a rabbit with a coding beat,
Hopping through changes, light and fleet.
Bumping versions with a joyful cheer,
New scripts and flows now appear.
Carrots and code, a perfect spree,
Celebrating updates with glee! 🥕💻

---

📜 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 56b9711 and 6235ee8.

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