chore: v2.0.0

[marcossevilla]

Status

READY

Description

Type of Change

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

Summary by CodeRabbit

• Documentation
  • Updated the changelog to announce version 2.0.0, highlighting support for Flutter 3.32.0 and a breaking change to the removeRouteBelow method.
• Chores
  • Bumped the package version to 2.0.0 in the configuration file.

[coderabbitai]

Walkthrough

The changes update the package version to 2.0.0 in both the changelog and pubspec.yaml, documenting support for Flutter 3.32.0 and a breaking change in the removeRouteBelow method signature. No code or dependency changes are introduced, only versioning and changelog updates.

Changes

File(s)	Change Summary
CHANGELOG.md	Added entry for version 2.0.0: supports Flutter 3.32.0, notes breaking change in removeRouteBelow.
pubspec.yaml	Updated package version from 1.0.0 to 2.0.0.

Possibly related PRs

• chore!: upgrade to Flutter 3.32.0 #98: Updates for Flutter 3.32.0 and related breaking changes, directly referenced in the changelog.

Poem

A hop and a skip, the version now two,
Flutter’s new magic—support shining through!
Changelog refreshed, the journey anew,
removeRouteBelow brings a change in view.
With every release, we leap to the sky—
🐇 Mockingjay soars, let’s give it a try!

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CHANGELOG.md (1)

3-3: Consider adding a release date
Including the release date next to the version entry can improve clarity and traceability for downstream users.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 388f94d and a6e363d.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• pubspec.yaml (1 hunks)

🔇 Additional comments (3)

pubspec.yaml (1)

3-3: Version bump to 2.0.0 looks good
The version: 2.0.0 update correctly aligns the package version with the new release.

CHANGELOG.md (2)

1-1: Changelog header is consistent
The # 2.0.0 entry matches the project’s existing format and syncs with the pubspec version.

---

5-5: Changelog bullet reference is accurate
The entry correctly points to PR #98 for the Flutter 3.32.0 upgrade, matching the recorded change.