Add CONTRACT_VERSION semantic-versioning check rejecting upgrade if breaking-major regression detected

[thlpkee20-wq]

Description

Today there is no programmatic check that an upgrade does not regress major version. Encode CONTRACT_VERSION semver and have migrate_storage reject upgrades whose to.major < from.major.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Relevant code: Revora-Contracts/src/lib.rs, Revora-Contracts/src/test_storage_layout_version.rs
• Use a (u32, u32, u32) triple for semver to avoid string parsing

Suggested execution

• Fork the repo and create a branch
• git checkout -b feat/semver-upgrade-guard
• Implement changes
  • Replace CONTRACT_VERSION: u32 with (MAJOR, MINOR, PATCH)
  • Add assert_semver_forward(from, to) helper
  • Reject downgrade with VersionDowngrade
• Validate security and correctness assumptions

Test and commit

• Run tests
  • cargo test --all
• Cover edge cases
  • Same-version migration must reject NoOpMigration
• Include test output and security notes

Example commit message

feat: enforce semver forward-only contract upgrades

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[ayo-ola0710]

@ayo-ola0710 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, can i take these please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ayo-ola0710 to this issue.

[yunus-dev-codecrafter]

@yunus-dev-codecrafter has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi! I've carefully reviewed the entire task description and fully understand the requirements and expected outcome.
I have experience working on similar tasks and I'm confident I can complete this within about an hour. I'd be happy to take ownership of this issue and submit a clean, well-tested solution promptly.
If it's available, please assign it to me. Thank you!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @yunus-dev-codecrafter to this issue.

[bbjiggy]

@bbjiggy has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue.

My approach would be to replace the current CONTRACT_VERSION: u32 with a (u32, u32, u32) semantic version tuple to enable explicit, type-safe version comparisons without string parsing. I'll implement an assert_semver_forward(from, to) helper that enforces forward-only upgrades, rejects major version downgrades with VersionDowngrade, and prevents no-op migrations by returning NoOpMigration when the versions are identical. I'll integrate these checks into migrate_storage while keeping the implementation minimal and easy to review. Finally, I'll add comprehensive tests covering valid upgrades, major downgrades, same-version migrations, and other edge cases, run cargo test --all, and include security notes documenting the upgrade invariants and assumptions.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @bbjiggy to this issue.

[grantfox-oss]

🦊 GrantFox — @yunus-dev-codecrafter has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #483)
2. Your PR will be reviewed by the RevoraOrg maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @yunus-dev-codecrafter! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @yunus-dev-codecrafter: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊