Skip to content

chore: bump versions (events 1.4.0, profile 1.2.0) ahead of testnet redeploy#98

Merged
0xdevcollins merged 1 commit into
testnetfrom
chore/version-bump-1.4.0
Jul 23, 2026
Merged

chore: bump versions (events 1.4.0, profile 1.2.0) ahead of testnet redeploy#98
0xdevcollins merged 1 commit into
testnetfrom
chore/version-bump-1.4.0

Conversation

@0xdevcollins

Copy link
Copy Markdown
Collaborator

Reconciles and bumps the on-chain version stamps so the next testnet deployment reports a coherent version.

Why

The stamps had drifted and were internally inconsistent:

Changes

Bumped coherently across INITIAL_VERSION, contractmeta, and the Cargo package version:

Contract Old New Since-last-version changes
events 1.3.0 (meta 1.2.0) 1.4.0 submission cap (#86), manager two-step (#88), OpSeen namespacing (#96)
profile 1.1.0 1.2.0 namespaced OpSeen (#95)

version()-asserting admin tests updated to match.

Verification

  • cargo test --workspace: 225 events + 66 profile green
  • make build (stellar-cli 27): events 56,091 B, profile 15,893 B — both under the 64 KB ceiling
  • cargo fmt --check clean

Deploy note (context, not part of this PR)

The on-chain testnet contracts currently report 0.4.0 / 0.2.0 — they predate the credit removal and are storage-incompatible with current HEAD (dropped credit fields + sdk 23→27). So the testnet refresh should be a fresh redeploy, not an in-place H6 upgrade (which would fail to decode the old rows). This PR only prepares the version stamps; the deploy is run separately.

🤖 Generated with Claude Code

…ractmeta

Version stamps had drifted and were internally inconsistent: events
contractmeta said 1.2.0 while INITIAL_VERSION said 1.3.0, and neither
reflected the public-surface / storage changes merged since (#86 submission
cap, #88 manager two-step, #96 OpSeen namespacing). Profile was still 1.1.0
despite #95 namespacing its OpSeen.

Bump both contracts coherently — INITIAL_VERSION, contractmeta, and the
Cargo package version all set to:
  events  1.3.0 -> 1.4.0   (submission cap, manager two-step, OpSeen ns)
  profile 1.1.0 -> 1.2.0   (namespaced OpSeen)

version()-asserting admin tests updated to match. 225 events + 66 profile
tests green; make build OK (events 56,091 B, profile 15,893 B, both under
the 64 KB ceiling); fmt clean.
@almanax-ai

almanax-ai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Quota reached

Your plan allows 300 CI/CD file units per month. You've used 297 and this scan would add 9 more (total: 306).

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@0xdevcollins, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 148e4845-5331-4ce7-b670-f4898939d564

📥 Commits

Reviewing files that changed from the base of the PR and between ba4e704 and 4ee394d.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (8)
  • contracts/events/Cargo.toml
  • contracts/events/src/admin.rs
  • contracts/events/src/lib.rs
  • contracts/events/src/tests/admin.rs
  • contracts/profile/Cargo.toml
  • contracts/profile/src/admin.rs
  • contracts/profile/src/lib.rs
  • contracts/profile/src/tests/admin.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/version-bump-1.4.0

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

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

@0xdevcollins
0xdevcollins merged commit eed33cf into testnet Jul 23, 2026
4 checks passed
@0xdevcollins
0xdevcollins deleted the chore/version-bump-1.4.0 branch July 23, 2026 18:44
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.

1 participant