chore: Merge Release v1.1.0 to main

[tirumerla]

Summary

• Merge release branch to main

Summary by CodeRabbit

• Release
  • Version 1.1.0 now available with new features and improvements
  • All documentation and references updated to reflect the latest release version
  • Changelog provides comprehensive documentation of features and bug fixes included in this release

[coderabbitai]

Walkthrough

The pull request bumps the project version from 1.0.0 to 1.1.0 across release configuration files, package manifests, and documentation references. No functional code changes are introduced.

Changes

Cohort / File(s)	Summary
Release and Package Versioning .github/release-please/manifest.json, Cargo.toml	Version number incremented from 1.0.0 to 1.1.0 in both release manifest and Cargo manifest
Changelog CHANGELOG.md	New changelog entry added documenting version 1.1.0 features and bug fixes
Documentation docs/antora.yml, docs/modules/ROOT/nav.adoc	Version references updated from 1.0.x to 1.1.x in Antora configuration; technical documentation link updated from release-v1-0-0 to release-v1-1-0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A whisker-twitch, a version leap,
From one-oh-oh to one-point-one so sweet,
The CHANGELOG chirps with tales untold,
Release and docs now proudly bold! 🎉

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description is largely incomplete compared to the template. The author provided only a "Summary" section with a single bullet point ("Merge release branch to main"), but the required template specifies three major sections: Summary, Testing Process, and Checklist. The Testing Process section is entirely missing, and the Checklist section with its required items is completely absent. While the provided summary line is on-topic, the overall description fails to follow the repository's template structure and lacks the information needed for proper review and verification.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The PR title "chore: Merge Release v1.1.0 to main" clearly and specifically describes the main change in the changeset. The pull request updates version information across multiple files (Cargo.toml, manifest.json, documentation files) and adds a CHANGELOG entry for version 1.1.0, which is exactly what the title indicates. The title is concise, follows conventional commit format, and avoids vague or generic language. A teammate scanning the repository history would immediately understand that this PR merges the release version 1.1.0 into the main branch.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-v1.1.0

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 47938d1 and 28d973d.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (5)

• .github/release-please/manifest.json (1 hunks)
• CHANGELOG.md (1 hunks)
• Cargo.toml (1 hunks)
• docs/antora.yml (1 hunks)
• docs/modules/ROOT/nav.adoc (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). (9)

• GitHub Check: test
• GitHub Check: clippy
• GitHub Check: msrv
• GitHub Check: boostsecurity - boostsecurityio/semgrep-pro
• GitHub Check: Redirect rules - openzeppelin-monitor
• GitHub Check: Header rules - openzeppelin-monitor
• GitHub Check: Pages changed - openzeppelin-monitor
• GitHub Check: Analyze (rust)
• GitHub Check: semgrep/ci

🔇 Additional comments (5)

docs/antora.yml (1)

4-4: Version bump is correct and consistent.

The Antora documentation version has been properly updated to match the release version in Cargo.toml and other manifests.

Cargo.toml (1)

3-3: Version bump is correct.

The package version has been properly updated to 1.1.0. Dependency versions remain pinned with appropriate security notes (line 22), which is good practice.

docs/modules/ROOT/nav.adoc (1)

11-11: Documentation link correctly updated for new release.

The technical Rust documentation link now points to the release-v1-1-0 build, with proper URL encoding maintained.

.github/release-please/manifest.json (1)

1-1: Release manifest version correctly updated.

The release-please manifest has been updated to reflect version 1.1.0, maintaining consistency across all release configuration files.

CHANGELOG.md (1)

3-3: Changelog structure is correct; verify entry overlap with 1.0.0 section.

The new 1.1.0 changelog entry is properly formatted with 31 features and 41 bug fixes. However, several entries appear to overlap with the 1.0.0 section below (e.g., "add block tracker" at line 8 also appears at line 85). This duplication may be intentional if features span development cycles, or it may be a release-please artifact. Confirm this aligns with your release strategy.

Also applies to: 6-78

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.6%. Comparing base (47938d1) to head (28d973d).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main    #387     +/-   ##
=======================================
+ Coverage   96.0%   96.6%   +0.5%     
=======================================
  Files         76      76             
  Lines      27116   26631    -485     
=======================================
- Hits       26048   25740    -308     
+ Misses      1068     891    -177     

Flag	Coverage Δ
integration	58.4% <ø> (-2.6%)	⬇️
properties	31.2% <ø> (?)
unittests	89.1% <ø> (+2.1%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.