release: 2.2.0-beta.2

[dev-jodee]

• Includes hotfix from main
• Includes estimate bundle fee for jito bundles

---

Important

Update to version 2.2.0-beta.2, add Jito bundle fee estimation, and fix transaction error.

• Version Update:
  • Update version to 2.2.0-beta.2 in Cargo.toml, crates/cli/Cargo.toml, crates/lib/Cargo.toml, and sdks/ts/package.json.
  • Update dependency version to 0.2.0-beta.2 in examples/jito-bundles/client/package.json.
• Features:
  • Add estimate fee for Jito bundle endpoint (PRO-638).
• Hotfix:
  • Fix error caused by big transaction when using v0 transaction (PRO-639).
• Documentation:
  • Add Jito bundle example code to CHANGELOG.md.

^{This description was created by for 20897f8. You can customize this summary. It will automatically update as commits are pushed.}

📊 Unit Test Coverage

Unit Test Coverage: 81.9%

View Detailed Coverage Report

[github-actions]

📊 TypeScript Coverage Report

Coverage: 80.3%

View detailed report

Coverage artifacts have been uploaded to this workflow run.
View Artifacts

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 60133dc in 59 seconds. Click for details.

• Reviewed 112 lines of code in 6 files
• Skipped 0 files when reviewing.
• Skipped posting 4 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. Cargo.toml:15

• Draft comment:
  The workspace package versions and dependency overrides have been updated consistently to "2.2.0-beta.2". This looks great; the explicit listing of workspace dependencies ensures consistent versions across all crates.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. crates/cli/Cargo.toml:1

• Draft comment:
  The CLI package’s version and metadata are updated appropriately. The bin section and docs feature using 'dep:utoipa' look nicely configured.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

3. crates/lib/Cargo.toml:1

• Draft comment:
  The core library is updated to "2.2.0-beta.2" and workspace dependencies are referenced correctly. The additional binary for "update-config" is still declared, which is fine.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

4. sdks/ts/package.json:1

• Draft comment:
  The TypeScript SDK package version is bumped to "0.2.0-beta.2" and the scripts, peerDependencies, and devDependencies are well maintained.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_2CNQGLm5zu4Y1oCZ

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[greptile-apps]

Greptile Overview

Greptile Summary

This is a release PR that bumps the version from 2.2.0-beta.1 to 2.2.0-beta.2 across all workspace crates and the TypeScript SDK. The PR includes:

Version Updates:

• Rust workspace crates: 2.2.0-beta.1 → 2.2.0-beta.2
• TypeScript SDK: 0.2.0-beta.1 → 0.2.0-beta.2 (uses independent versioning)
• All version updates are consistent across: root Cargo.toml, crates/cli/Cargo.toml, crates/lib/Cargo.toml, Cargo.lock, and sdks/ts/package.json

Included Changes (from base branch):
The release consolidates three PRs that were already merged to the release/2.2.0 branch:

1. docs: add jito bundle example code #295: Documentation - Added Jito bundle example code
2. feat: (PRO-638) Estimate fee for Jito bundle endpoint #296: Feature - Implemented estimateBundleFee endpoint for Jito bundle fee estimation
3. hotfix: (PRO-639) Fix big transaction causing error when using v0 tra… #297: Hotfix - Fixed transaction serialization error for large V0 transactions by removing workaround for resolved Agave validator issue

Review Findings:

• ✅ Version numbers are consistent across all files
• ✅ Changelog entries accurately reflect the included PRs
• ⚠️ The changelog uses a "Hotfix" section heading that is not defined in the git-cliff configuration (.github/cliff.toml), which could cause inconsistencies in future automated changelog generation

The version bump follows the standard beta release pattern and maintains backward compatibility with the existing release workflow.

Confidence Score: 4/5

• This PR is safe to merge with minimal risk - it's a straightforward version bump with one minor changelog formatting inconsistency
• Score of 4 reflects that this is a well-structured release PR with correct version updates across all files. The one point deduction is due to the changelog format inconsistency where the "Hotfix" section heading doesn't align with the git-cliff configuration. This is a non-critical style issue that won't affect functionality but should be addressed to maintain consistency with the automated changelog generation system.
• CHANGELOG.md needs minor formatting adjustment to align with git-cliff configuration

Important Files Changed

File Analysis

Filename	Score	Overview
CHANGELOG.md	4/5	Added release notes for 2.2.0-beta.2 with one format inconsistency in the 'Hotfix' section
Cargo.toml	5/5	Workspace version bumped to 2.2.0-beta.2, correctly propagates to all workspace members
crates/cli/Cargo.toml	5/5	CLI crate version correctly bumped to 2.2.0-beta.2
crates/lib/Cargo.toml	5/5	Library crate version correctly bumped to 2.2.0-beta.2
sdks/ts/package.json	5/5	TypeScript SDK version correctly bumped to 0.2.0-beta.2 (uses independent versioning)

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant PR as PR #298
    participant Base as release/2.2.0 Branch
    participant Rust as Rust Crates
    participant TS as TypeScript SDK
    participant CL as CHANGELOG.md

    Note over Dev,CL: Release Version Bump: 2.2.0-beta.2

    Dev->>Base: Merge PR #295 (Jito docs)
    Dev->>Base: Merge PR #296 (estimateBundleFee)
    Dev->>Base: Merge PR #297 (V0 tx hotfix)
    
    Note over Base: Base branch contains all features
    
    Dev->>PR: Create release PR
    PR->>Rust: Update workspace version
    Rust->>Rust: Cargo.toml: 2.2.0-beta.1 → 2.2.0-beta.2
    Rust->>Rust: crates/cli/Cargo.toml: 2.2.0-beta.1 → 2.2.0-beta.2
    Rust->>Rust: crates/lib/Cargo.toml: 2.2.0-beta.1 → 2.2.0-beta.2
    Rust->>Rust: Cargo.lock: Auto-update versions
    
    PR->>TS: Update SDK version
    TS->>TS: package.json: 0.2.0-beta.1 → 0.2.0-beta.2
    
    PR->>CL: Generate changelog
    CL->>CL: Add 2.2.0-beta.2 section
    CL->>CL: Document PR #295 (docs)
    CL->>CL: Document PR #296 (feat)
    CL->>CL: Document PR #297 (hotfix)
    
    Note over CL: ⚠️ "Hotfix" section not in git-cliff config
    
    PR->>Base: Ready for merge
    Base-->>Dev: Release 2.2.0-beta.2

Loading

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 20897f8 in 1 minute and 21 seconds. Click for details.

• Reviewed 19 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. examples/jito-bundles/client/package.json:18

• Draft comment:
  Updated dependency version to beta.2 looks good. Ensure this change is backward-compatible with existing integrations.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. examples/jito-bundles/client/package.json:25

• Draft comment:
  Please add a trailing newline at end-of-file to follow best practices.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% The comment is about a stylistic/formatting issue - the lack of a trailing newline. While this is technically a "best practice," it's a very minor formatting issue. The rules state "Do NOT make comments that are obvious or unimportant." A missing trailing newline is typically caught by linters/formatters and is quite minor. However, the rules also say "Comments that suggest code quality refactors are good! But only if they are actionable and clear." This is actionable and clear. But is it important enough? The rules emphasize not making obvious or unimportant comments. A trailing newline is a very minor issue that would typically be handled by automated tooling. This could be considered an actionable code quality suggestion that follows best practices. Many style guides and linters do enforce trailing newlines. It's a real change that was made (the newline was removed), so it is about the changes in the diff. While it is technically actionable, the rules explicitly state not to make "obvious or unimportant" comments. A missing trailing newline is extremely minor and would typically be caught by automated formatting tools. This falls into the category of unimportant comments that shouldn't clutter the review. This comment should be deleted. While it's technically correct and actionable, it's an unimportant formatting issue that falls under the "obvious or unimportant" rule. Such minor formatting issues are typically handled by automated tooling.

Workflow ID: wflow_6Y6cVdxKnUvuZd6S

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}