Skip to content

chore(events): bump to 1.5.0 (deadline enforcement removed)#100

Merged
0xdevcollins merged 1 commit into
testnetfrom
chore/events-1.5.0
Jul 23, 2026
Merged

chore(events): bump to 1.5.0 (deadline enforcement removed)#100
0xdevcollins merged 1 commit into
testnetfrom
chore/events-1.5.0

Conversation

@0xdevcollins

Copy link
Copy Markdown
Collaborator

#99 removed on-chain submission-deadline enforcement (a real behavior change) but didn't bump the version. Bump events 1.4.0 → 1.5.0 across INITIAL_VERSION, contractmeta, and the Cargo package version so the next testnet upgrade reports a coherent version(). Profile untouched by #99 → stays 1.2.0.

version()-asserting admin tests updated; admin suite green, fmt clean.

🤖 Generated with Claude Code

#99 changed contract behavior (submission deadline no longer enforced on
chain) without a version bump. Bump events 1.4.0 -> 1.5.0 across
INITIAL_VERSION, contractmeta, and the Cargo package version so the next
testnet upgrade stamps a coherent version. Profile is unchanged by #99 and
stays 1.2.0.
@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 5 more (total: 302).

@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: 53 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: dd5476c5-0075-493b-a99d-e409d0a4f17f

📥 Commits

Reviewing files that changed from the base of the PR and between 92eb157 and db05128.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (4)
  • contracts/events/Cargo.toml
  • contracts/events/src/admin.rs
  • contracts/events/src/lib.rs
  • contracts/events/src/tests/admin.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/events-1.5.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 8e15770 into testnet Jul 23, 2026
4 checks passed
@0xdevcollins
0xdevcollins deleted the chore/events-1.5.0 branch July 23, 2026 20:18
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