Skip to content

Conversation

@GabrielePicco
Copy link
Collaborator

@GabrielePicco GabrielePicco commented Oct 12, 2025

Summary by CodeRabbit

  • Chores
    • Bumped package version to 0.2.2 across the npm package and Rust workspace.
    • Updated platform-specific validator binary references to 0.2.2 for macOS (Apple Silicon, Intel), Linux (ARM64, x64), and Windows (x64).
    • No functional or behavior changes; maintenance release focused on version alignment.

Greptile Overview

Updated On: 2025-10-12 07:27:32 UTC

Summary

Release version bump from 0.2.1 to 0.2.2 across all workspace packages and NPM distributions.

Key Changes:

  • Updated workspace version in Cargo.toml
  • Updated NPM package version and all platform-specific dependencies (darwin-arm64, darwin-x64, linux-arm64, linux-x64, windows-x64)
  • Regenerated lock files with version updates

Concerns:

  • Two dependency downgrades detected in Cargo.lock: hashbrown (0.13.2→0.12.3) and windows-core (0.61.2→0.56.0)
  • Verify these downgrades are intentional and don't introduce compatibility issues

Confidence Score: 4/5

  • This release PR is generally safe to merge with minor concerns about dependency downgrades
  • The version bump is consistent across all files (Rust workspace and NPM packages). However, two dependency downgrades (hashbrown and windows-core) in Cargo.lock warrant verification before merging to ensure they don't introduce compatibility issues or vulnerabilities
  • Verify Cargo.lock dependency downgrades are intentional and don't break compatibility

Important Files Changed

File Analysis

Filename Score Overview
Cargo.toml 5/5 Workspace version bumped from 0.2.1 to 0.2.2 consistently
.github/packages/npm-package/package.json 5/5 Package version and all platform-specific dependencies updated to 0.2.2
.github/packages/npm-package/package.json.tmpl 5/5 Template version updated to 0.2.2 for NPM package generation
Cargo.lock 3/5 Version updates with unexpected dependency downgrades (hashbrown 0.13.2→0.12.3, windows-core 0.61.2→0.56.0)
test-integration/Cargo.lock 3/5 Version updates with hashbrown downgrade and magicblock-magic-program-api source changes

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant CT as Cargo.toml
    participant NPM as NPM Package Files
    participant CL as Cargo.lock Files
    participant CI as CI/CD Pipeline

    Dev->>CT: Update workspace version to 0.2.2
    Dev->>NPM: Update package.json version to 0.2.2
    Dev->>NPM: Update package.json.tmpl version to 0.2.2
    Dev->>NPM: Update all platform dependencies to 0.2.2
    
    Dev->>CL: Run cargo update
    CL-->>CL: Regenerate Cargo.lock
    CL-->>CL: Update all workspace crate versions
    Note over CL: Side effect: hashbrown 0.13.2→0.12.3
    Note over CL: Side effect: windows-core 0.61.2→0.56.0
    
    Dev->>CL: Update test-integration/Cargo.lock
    CL-->>CL: Update integration test dependencies
    
    Dev->>CI: Commit release 0.2.2
    CI->>CI: Build and test all platforms
    CI->>CI: Publish NPM packages
    CI->>CI: Create release artifacts
Loading

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 12, 2025

Walkthrough

Version increments from 0.2.1 to 0.2.2 across npm package files and Cargo workspace. Optional dependency versions for platform-specific ephemeral-validator binaries are updated in the npm package.

Changes

Cohort / File(s) Summary
NPM package version bump
\.github/packages/npm-package/package.json, \.github/packages/npm-package/package.json.tmpl
Update "version" to 0.2.2; bump optionalDependencies for ephemeral-validator-* targets from 0.2.1 to 0.2.2.
Cargo workspace version bump
Cargo.toml
Update [workspace.package] version from 0.2.1 to 0.2.2.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my whiskers—version two dot two,
Hops through fields where semvers grew.
Tiny bumps on tidy trails,
Carrots packed for all the builds and rails.
With thump-thump joy, I sign and cheer—
Ship it swift, the path is clear! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The pull request title succinctly indicates the version bump to 0.2.2, directly reflecting the primary change in the changeset and providing clear context for reviewers scanning the history.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release/v0.2.2

📜 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 d0499a6 and 0fe3432.

⛔ Files ignored due to path filters (2)
  • Cargo.lock is excluded by !**/*.lock
  • test-integration/Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • .github/packages/npm-package/package.json (2 hunks)
  • .github/packages/npm-package/package.json.tmpl (1 hunks)
  • Cargo.toml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)
  • GitHub Check: run_make_ci_format
  • GitHub Check: run_make_ci_test
  • GitHub Check: run_make_ci_lint
  • GitHub Check: run_make_ci_test
  • GitHub Check: Publish Binaries (darwin-x64, macos-latest, stable, x86_64-apple-darwin)
  • GitHub Check: Publish Binaries (linux-x64-glibc, ubuntu-latest, stable, x86_64-unknown-linux-gnu)
  • GitHub Check: Publish Binaries (win32-x64-msvc, windows-latest, stable, x86_64-pc-windows-msvc)
  • GitHub Check: Publish Binaries (darwin-arm64, macos-latest, stable, aarch64-apple-darwin)
  • GitHub Check: Publish Binaries (linux-arm64-glibc, arm64, stable, aarch64-unknown-linux-gnu)
🔇 Additional comments (4)
Cargo.toml (1)

54-54: LGTM! Workspace version updated correctly.

The version bump to 0.2.2 is consistent with the other files in this PR.

.github/packages/npm-package/package.json.tmpl (1)

4-4: LGTM! Template version updated correctly.

The version bump to 0.2.2 is consistent with the Cargo workspace and main npm package.

.github/packages/npm-package/package.json (2)

3-3: LGTM! Main package version updated correctly.

The version bump to 0.2.2 is consistent across the entire PR.


31-35: All platform-specific dependencies updated; no further package.json version references found
Search results only show “0.2.1” in Rust lockfiles (Cargo.lock/TOML), which don’t require manual updates for this npm bump.


Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link

Manual Deploy Available

You can trigger a manual deploy of this PR branch to testnet:

Deploy to Testnet 🚀

Alternative: Comment /deploy on this PR to trigger deployment directly.

⚠️ Note: Manual deploy requires authorization. Only authorized users can trigger deployments.

Comment updated automatically when the PR is synchronized.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

3 files reviewed, 2 comments

Edit Code Review Agent Settings | Greptile

dependencies = [
"borsh-derive 0.10.4",
"hashbrown 0.13.2",
"hashbrown 0.12.3",
Copy link
Contributor

Choose a reason for hiding this comment

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

style: downgrade from hashbrown 0.13.2 to 0.12.3 in borsh dependencies - verify this is intentional

Prompt To Fix With AI
This is a comment left during a code review.
Path: Cargo.lock
Line: 814:814

Comment:
**style:** downgrade from `hashbrown 0.13.2` to `0.12.3` in borsh dependencies - verify this is intentional

How can I resolve this? If you propose a fix, please make it concise.

"log",
"wasm-bindgen",
"windows-core 0.61.2",
"windows-core 0.56.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

style: downgrade from windows-core 0.61.2 to 0.56.0 - verify this is intentional

Prompt To Fix With AI
This is a comment left during a code review.
Path: Cargo.lock
Line: 3006:3006

Comment:
**style:** downgrade from `windows-core 0.61.2` to `0.56.0` - verify this is intentional

How can I resolve this? If you propose a fix, please make it concise.

@GabrielePicco GabrielePicco merged commit 385d55a into master Oct 12, 2025
13 checks passed
@GabrielePicco GabrielePicco deleted the release/v0.2.2 branch October 12, 2025 09:35
@coderabbitai coderabbitai bot mentioned this pull request Oct 13, 2025
thlorenz added a commit that referenced this pull request Oct 13, 2025
* master:
  release: 0.2.3 (#571)
  fix: release package with CI (#570)
  release: 0.2.2 (#568)
  feat: add cli command to run the solana-test-validator with ER setup (#567)
  fix: periodic committer attempts to commit undelegated accounts & sqlite INTEGER overflow (#556)
  feat: schedule tasks (#493)
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.

2 participants