[bmuddha]

What changed

Prepare 2.0.0-rc.1 for testing by aligning the workspace version, local Cargo lockfile entries, and npm manifests. Release preparation now accepts -rc.N, orders RC updates correctly, and allows promotion to the corresponding stable version.

Impact

RC tags create draft GitHub prereleases and are never marked Latest. Binary, npm, and crate publication is blocked for RC versions, including manual workflow runs, and for releases marked prerelease.

Reviewer notes

This RC will remain in draft; it is not intended for publication. The public release will be prepared separately as v2.0.0. External dependency versions are unchanged.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

Release workflows now accept release-candidate versions, select stable or RC versions during release preparation, and apply prerelease-specific rules when creating and publishing releases. Workspace and npm package versions change to 2.0.0-rc.1.

Changes: RC Release Support

Layer / File(s)	Summary
RC version declarations and validation Cargo.toml, .github/packages/npm-package/package.json, .github/packages/npm-package/package.json.tmpl, .github/scripts/workspace-version.sh	Workspace and npm package versions change to 2.0.0-rc.1. Workspace version validation accepts an RC suffix with a positive integer and no leading zeroes.
Release version selection .github/workflows/prepare-release.yml	Release preparation accepts stable and RC versions. Without an explicit version, an RC defaults to its corresponding stable version, while a stable version defaults to the next patch. Explicit versions must be newer.
RC release publishing rules .github/workflows/release-tag.yml, .github/workflows/publish-packages.yml	RC releases are created as prereleases, excluded from binary publishing, and marked not latest.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Other

Possibly related PRs

• magicblock-labs/magicblock-validator#1856: This PR continues the workspace and npm version updates from that PR and adds RC release handling.

Suggested reviewers: gabrielepicco, snawaz

Merge Risk: Minimal · up to acd75

The RC changes support version ordering and stable promotion while preventing RC package publication. No concrete merge-blocking risk remains after normal checks.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title "chore: prepare v2.0.0-rc.1 for testing" matches the main change. The PR sets the workspace, npm, and Cargo versions to 2.0.0-rc.1 and updates the release workflows to handle RC versions. Th…
Description check		The description states that the PR prepares 2.0.0-rc.1 by aligning the workspace version, lockfile entries, and npm manifests. It also explains the RC release-workflow changes, the publication blocks …
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title "chore: prepare v2.0.0-rc.1 for testing" matches the main change. The PR sets the workspace, npm, and Cargo versions to 2.0.0-rc.1 and updates the release workflows to handle RC versions. The title names the version bump but does not mention the workflow changes that block RC publication.

Full details: Description check

Explanation

The description states that the PR prepares 2.0.0-rc.1 by aligning the workspace version, lockfile entries, and npm manifests. It also explains the RC release-workflow changes, the publication blocks for RC and prerelease versions, and the reviewer notes. It is directly related to the changeset.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 1 files. (6 skipped: 6 unsupported.)

Finishing Touches

Generate docstrings

• Commit to this branch
• Create a new PR

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

Recent review info

Run configuration

• Source mode: Auto
• Repository: magicblock-labs/magicblock-validator
• Branch: chore/prepare-v2.0.0-rc.1
• File: .coderabbit.yaml
• Commit: acd7593
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 6238fb17-72bb-4a29-99d9-5212fbf867bd

Commits

Reviewing files that changed from the base of the PR and between 7b3eb74 and acd7593.

Files ignored due to path filters: 1

• Cargo.lock is excluded by !**/*.lock

Files selected for processing: 7

• .github/packages/npm-package/package.json
• .github/packages/npm-package/package.json.tmpl
• .github/scripts/workspace-version.sh
• .github/workflows/prepare-release.yml
• .github/workflows/publish-packages.yml
• .github/workflows/release-tag.yml
• Cargo.toml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.