4.3.0 release

[khancode]

High Level Overview of Change

4.3.0 release

Context of Change

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Tests (You added tests for code that already exists, or your new feature included in this PR)
• Documentation Updates
• Release

Did you update HISTORY.md?

• Yes
• No, this change does not impact library users

Test Plan

[coderabbitai]

Walkthrough

This change adds new released version entries for 2.4.0 in ripple-binary-codec and 4.3.0 in xrpl to their respective changelog files, both dated June 9, 2025. The package versions were updated accordingly, and the xrpl package updated its dependency on ripple-binary-codec to the new version. No other code or metadata changes were made.

Changes

Files	Change Summary
packages/ripple-binary-codec/HISTORY.md	Added released version entry for 2.4.0 (2025-06-09)
packages/xrpl/HISTORY.md	Added released version entry for 4.3.0 (2025-06-09)
packages/ripple-binary-codec/package.json	Updated package version from 2.3.0 to 2.4.0
packages/xrpl/package.json	Updated package version from 4.2.5 to 4.3.0; upgraded ripple-binary-codec dependency from ^2.3.0 to ^2.4.0

Possibly related PRs

• 4.1.0 release #2851: Updates package versions and changelog entries for ripple-binary-codec and xrpl to newer unreleased versions, similar in nature but for earlier releases.
• 4.2.0 release #2896: Introduces new features and amendments in ripple-binary-codec and xrpl for earlier versions; related by version progression but no overlapping code changes.

Suggested reviewers

• pdp2121
• achowdhry-ripple

Poem

A hop and a skip, a changelog anew,
Two versions appear, with nothing else to do.
No code was disturbed, no features unfurled,
Just dates and some numbers, announced to the world.
🐇✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5a1ecae and ed877ce.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• packages/ripple-binary-codec/HISTORY.md (1 hunks)
• packages/ripple-binary-codec/package.json (1 hunks)
• packages/xrpl/HISTORY.md (1 hunks)
• packages/xrpl/package.json (2 hunks)

✅ Files skipped from review due to trivial changes (1)

• packages/xrpl/HISTORY.md

🚧 Files skipped from review as they are similar to previous changes (3)

• packages/ripple-binary-codec/HISTORY.md
• packages/ripple-binary-codec/package.json
• packages/xrpl/package.json

⏰ Context from checks skipped due to timeout of 90000ms (7)

• GitHub Check: integration (20.x)
• GitHub Check: integration (22.x)
• GitHub Check: unit (20.x)
• GitHub Check: browser (22.x)
• GitHub Check: unit (22.x)
• GitHub Check: build-and-lint (22.x)
• GitHub Check: Analyze (javascript)

---

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.

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

packages/ripple-binary-codec/HISTORY.md (1)

5-6: Confirm new release entry for 2.4.0
Added the ## 2.4.0 (2025-6-09) header under Unreleased correctly.

Consider standardizing the date format across changelog entries to a consistent YYYY-MM-DD style for clarity.

packages/xrpl/HISTORY.md (1)

7-7: Confirm new release entry for 4.3.0
The ## 4.3.0 (2025-6-09) header is correctly placed under Unreleased.

Align date formatting with the rest of the changelog (e.g., use YYYY-MM-DD) for consistency.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9a997c8 and 6f3c808.

📒 Files selected for processing (2)

• packages/ripple-binary-codec/HISTORY.md (1 hunks)
• packages/xrpl/HISTORY.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (7)

• GitHub Check: integration (20.x)
• GitHub Check: integration (22.x)
• GitHub Check: unit (20.x)
• GitHub Check: browser (22.x)
• GitHub Check: unit (22.x)
• GitHub Check: build-and-lint (22.x)
• GitHub Check: Analyze (javascript)