chore: solana-program cap <3.0.0

[jonasXchen]

Summary by CodeRabbit

• Chores
  • Updated solana-program dependency version constraints.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated the solana-program dependency version constraint in Cargo.toml from >=1.6 to >=1.6, <3.0.0, adding an upper bound to prevent compatibility issues with major version releases.

Changes

Cohort / File(s)	Change Summary
Dependency version constraint Cargo.toml	Updated solana-program version requirement to include upper bound (<3.0.0), restricting to major versions 1.x and 2.x

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

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 title accurately describes the main change: adding an upper version bound (<3.0.0) to the solana-program dependency in Cargo.toml.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch jonasXchen/solana-program-cap

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 28afe45 and 471b501.

📒 Files selected for processing (1)

• 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). (1)

• GitHub Check: test-and-build

🔇 Additional comments (1)

Cargo.toml (1)

20-20: Verify version constraint consistency across Solana dependencies.

The change adds an upper bound (<3.0.0) to solana-program, which is a good practice. However, other closely related Solana crates—solana-sdk (line 29) and solana-program-test (line 30)—still use open-ended constraints (>=1.6). Since Solana crates typically have coordinated releases, if solana-program 3.0.0 introduces breaking changes, solana-sdk and solana-program-test likely will too. This inconsistency could allow Cargo to resolve incompatible versions.

Please verify one of the following:

1. If other Solana crates should be capped: Apply the same upper bound (<3.0.0) to solana-sdk and solana-program-test for consistency and to prevent incompatible version combinations.

2. If the constraint is crate-specific: Confirm that solana-program has had breaking changes in major versions while solana-sdk and solana-program-test have not, justifying the asymmetric constraint.

You can verify this by checking the release notes or CHANGELOG for these crates in the official Solana repository.

Also applies to: 29-30

---

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

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