Bump frezeed to latest

[JarvanMo]

Description

Bump freezed to latest.

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

• Chores
  • Updated package versions for improved compatibility and stability.

[coderabbitai]

Walkthrough

The pubspec.yaml file was updated to increase the versions of the freezed_annotation and freezed packages. No other dependencies or configurations were modified.

Changes

Cohort / File(s)	Change Summary
Dependency Version Updates pubspec.yaml	Upgraded freezed_annotation from ^2.4.1 to ^3.1.0 and freezed from ^2.4.7 to ^3.2.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇✨
With a hop and a skip, dependencies grow,
Freezed hops higher, as versions now show.
Annotation in tow, both ready to run,
The codebase refreshed, the update is done!
In the garden of YAML, all’s up to date—
Time for a carrot, let’s celebrate!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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 generate unit tests to generate unit tests for 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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f0aeeca and ed9f9af.

📒 Files selected for processing (1)

• pubspec.yaml (2 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). (1)

• GitHub Check: pana / build

[coderabbitai]

⚠️ Potential issue

Align freezed and freezed_annotation to the same minor version

freezed enforces that freezed (code-gen) and freezed_annotation (runtime) share identical MAJOR and MINOR numbers.
Here you bump freezed_annotation to ^3.1.0 while the generator is ^3.2.0. This mismatch will cause build-runner to fail with
Unsupported Freezed version errors during code-generation.

Proposed fix:

-  freezed_annotation: ^3.1.0
+  freezed_annotation: ^3.2.0

(or downgrade the generator to ^3.1.0; keeping them identical is the key).

Also applies to: 25-25

🤖 Prompt for AI Agents

In pubspec.yaml around lines 16 to 17, the versions of freezed_annotation and
freezed are mismatched, causing build-runner errors. Ensure both freezed and
freezed_annotation dependencies have the same major and minor version numbers by
updating freezed_annotation to match the freezed version (e.g., both to ^3.2.0)
or downgrading freezed to ^3.1.0. This alignment will prevent the Unsupported
Freezed version error during code generation.