Skip to content

chore: new release v4.4.0-pre.0#7202

Merged
SWvheerden merged 1 commit intotari-project:developmentfrom
SWvheerden:sw_new_release
Jun 11, 2025
Merged

chore: new release v4.4.0-pre.0#7202
SWvheerden merged 1 commit intotari-project:developmentfrom
SWvheerden:sw_new_release

Conversation

@SWvheerden
Copy link
Copy Markdown
Collaborator

@SWvheerden SWvheerden commented Jun 11, 2025

Description

new release for esmeralda

Summary by CodeRabbit

  • Documentation
    • Updated README and changelogs to reflect new recommended and released versions for all networks, highlighting new features and bug fixes in version 4.4.0.
  • Chores
    • Bumped version numbers across multiple packages and configuration files from 4.3.1-pre.0 to 4.4.0-pre.0.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jun 11, 2025

Walkthrough

This update performs a coordinated version bump across multiple Cargo.toml files, configuration files, and documentation. Version numbers are incremented from 4.3.1-pre.0 to 4.4.0-pre.0 (and related release variants) for packages, network recommendations, and supply-chain exemptions. Changelog files are updated with new entries for version 4.4.0, detailing new features and bug fixes.

Changes

Files/Paths Change Summary
Cargo.toml, applications/minotari_ledger_wallet/comms/Cargo.toml, ... , infrastructure/test_utils/Cargo.toml, comms/rpc_macros/Cargo.toml Updated package version numbers from 4.3.1-pre.0 to 4.4.0-pre.0
README.md Updated recommended network version numbers to 4.4.0, 4.4.0-rc.0, and 4.4.0-pre.0
changelog-Mainnet.md, changelog-nextnet.md, changelog-development.md Added new changelog entries for 4.4.0, 4.4.0-rc.0, and 4.4.0-pre.0 with feature and bug fix summaries
supply-chain/config.toml Updated exemption version numbers from 4.3.1-pre.0 to 4.4.0-pre.0 for multiple components; criteria remain unchanged

Poem

🐇
A hop to four-point-four, we leap,
With changelogs tidy, versions neat.
New features bloom, old bugs retreat,
Our code refreshed, a rhythmic beat.
As carrots grow and ledgers gleam,
The rabbit grins—onward, team!


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

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
changelog-nextnet.md (1)

15-23: Inconsistent component tagging in Bug Fixes
The first bug fix entry uses a bold component prefix (**network-discovery:**), but the subsequent entries do not. For consistency, consider bolding component names and adding colons for all items.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between af1203a and 5e27cc9.

⛔ 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)
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: test (nextnet, nextnet)
  • GitHub Check: test (mainnet, stagenet)
  • GitHub Check: test (testnet, esmeralda)
  • GitHub Check: cargo check with stable
  • GitHub Check: ci
  • GitHub Check: Cucumber tests / FFI
  • GitHub Check: Cucumber tests / Base Layer
🔇 Additional comments (15)
applications/minotari_ledger_wallet/comms/Cargo.toml (1)

3-3: Bump minotari_ledger_wallet_comms version to 4.4.0-pre.0
Version update aligns with the coordinated prerelease.

infrastructure/test_utils/Cargo.toml (1)

4-4: Bump tari_test_utils version to 4.4.0-pre.0
Version update aligns with the coordinated prerelease.

comms/rpc_macros/Cargo.toml (1)

9-9: Bump tari_comms_rpc_macros version to 4.4.0-pre.0
Version update aligns with the coordinated prerelease.

applications/minotari_ledger_wallet/wallet/Cargo.toml (1)

3-3: Bump minotari_ledger_wallet version to 4.4.0-pre.0
Version update aligns with the coordinated prerelease.

Cargo.toml (1)

2-2: Bump workspace version to 4.4.0-pre.0
Version update aligns with the coordinated prerelease across all member crates.

applications/minotari_miner/Cargo.toml (1)

7-7: Bump package version to 4.4.0-pre.0
The version update aligns with the coordinated workspace-wide release and matches other Tari components’ versions.

README.md (1)

25-27: Update recommended network versions to 4.4.0 series
Mainnet, Nextnet, and Esmeralda entries have been correctly updated to 4.4.0, 4.4.0-rc.0, and 4.4.0-pre.0, respectively, ensuring consistency with the new release.

changelog-Mainnet.md (1)

5-6: Add changelog entry for v4.4.0 (2025-06-11)
The new section accurately documents the features and bug fixes for v4.4.0 and links from v4.3.1.

changelog-development.md (3)

5-5: Verify version header entry.

The new 4.4.0-pre.0 entry with its compare link and date looks correct. Ensure the link reference and date (2025-06-11) match the actual release metadata.


10-12: Approve feature list format.

The feature bullets are clear and properly linked with issue and commit references. Ensure consistency in phrasing if wider style changes are needed.


17-22: Approve bug fix entries.

All bug fixes are documented with appropriate issue and commit references. Confirm the bolded scopes and descriptions accurately reflect the merged changes.

changelog-nextnet.md (2)

5-5: Release entry bump looks correct.
Version number and compare URL are accurate, and the date aligns with the intended release.


8-12: Feature entries formatted properly.
The list under ### Features follows the project’s style and the links to issues and commits are well-formed.

supply-chain/config.toml (2)

1575-1634: Consistent version bump for all minotari_* exemptions
All minotari_app_grpc, minotari_app_utilities, minotari_console_wallet, minotari_merge_mining_proxy, minotari_miner, minotari_mining_helper_ffi, minotari_wallet, and minotari_wallet_ffi exemptions have been uniformly updated from 4.3.1-pre.0 to 4.4.0-pre.0 and retain the safe-to-deploy criteria. This aligns with the coordinated release bump.


2675-2830: Consistent version bump for all tari_* exemptions
Each tari_common, tari_common_sqlite, tari_common_types, tari_comms, tari_comms_dht, tari_comms_rpc_macros, tari_contacts, tari_core, tari_features, tari_hashing, tari_key_manager, tari_libtor, tari_metrics, tari_mmr, tari_p2p, tari_script, tari_service_framework, tari_shutdown, tari_storage, and tari_test_utils exemption has been correctly bumped to 4.4.0-pre.0 with no other changes. Matches the release update across Cargo.toml files.

Comment on lines 24 to 26
### [4.3.1-rc.0](https://github.com/tari-project/tari/compare/v4.3.0-rc.0...v4.3.1-rc.0) (2025-06-03)


Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Incorrect heading level for previous release
The entry for 4.3.1-rc.0 is marked with ###, which conflicts with the ## used for other version headings. It should be at the same level.

-### [4.3.1-rc.0](https://github.com/tari-project/tari/compare/v4.3.0-rc.0...v4.3.1-rc.0) (2025-06-03)
+## [4.3.1-rc.0](https://github.com/tari-project/tari/compare/v4.3.0-rc.0...v4.3.1-rc.0) (2025-06-03)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### [4.3.1-rc.0](https://github.com/tari-project/tari/compare/v4.3.0-rc.0...v4.3.1-rc.0) (2025-06-03)
## [4.3.1-rc.0](https://github.com/tari-project/tari/compare/v4.3.0-rc.0...v4.3.1-rc.0) (2025-06-03)
🤖 Prompt for AI Agents
In changelog-nextnet.md around lines 24 to 26, the heading for version
4.3.1-rc.0 is using ### instead of ##, which is inconsistent with other version
headings. Change the heading level from ### to ## to match the format used for
other release entries.

@SWvheerden SWvheerden merged commit 006015a into tari-project:development Jun 11, 2025
15 checks passed
sdbondi added a commit to sdbondi/tari that referenced this pull request Jun 18, 2025
* development: (607 commits)
  Wallet GRPC port comment fix from 18142 to 18143 (tari-project#7221)
  feat: integrated address support for Ledger (tari-project#7198)
  chore: new release v4.1.1-pre.0 (tari-project#7211)
  fix: migration can now correctly resume after stopping (tari-project#7210)
  fix: only revalidated rejected transactions on startup (tari-project#7209)
  fix: add filtering flag back (tari-project#7208)
  feat: improve wallet balance checks from external clients (tari-project#7207)
  feat!: update grpc supply query (tari-project#7137)
  docs: Updated API GRPC and Exchange Guide (tari-project#7205)
  chore: new release v4.4.0-pre.0 (tari-project#7202)
  feat: update base node proto to search bytes (tari-project#7201)
  feat: full PayRef implementation (tari-project#7154)
  test: add ffi cucumber wallet balance test (tari-project#7189)
  chore: fix tests (tari-project#7196)
  fix(network-discovery): add back idle event handling (tari-project#7194)
  Update SECURITY.md (tari-project#7193)
  fix: transaction manager service unmined lookup (tari-project#7192)
  fix: wallet ffi database name mismatch for mobile wallet (tari-project#7191)
  fix: payment_id deserialize (tari-project#7187)
  fix: remove code for deleting stale peers (tari-project#7184)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant