chore(deps): update dependency riverpod_generator to v2.6.4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
riverpod_generator	dev_dependencies	patch	2.6.3 -> 2.6.4

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

rrousselGit/riverpod (riverpod_generator)

v2.6.4

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: app/mobile/pubspec.lock

Command failed: flutter pub upgrade riverpod_generator
Because riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on source_gen ^2.0.0 and go_router_builder 2.7.1 depends on source_gen ^1.0.0, riverpod_generator >=2.6.4 <3.0.0-dev.2 is incompatible with go_router_builder 2.7.1.
So, because app_mobile depends on both go_router_builder 2.7.1 and riverpod_generator 2.6.4, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on riverpod_generator: flutter pub add dev:riverpod_generator:^2.6.3
Failed to update packages.

File name: core/analytics/pubspec.lock

Command failed: dart pub upgrade riverpod_generator
Because riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on analyzer ^7.0.0 and build_runner 2.4.13 depends on analyzer >=4.4.0 <7.0.0, riverpod_generator >=2.6.4 <3.0.0-dev.2 is incompatible with build_runner 2.4.13.
So, because core_analytics depends on both build_runner 2.4.13 and riverpod_generator 2.6.4, version solving failed.


You can try one of the following suggestions to make the pubspec resolve:
* Try upgrading your constraint on build_runner: dart pub add dev:build_runner:^2.4.14
* Consider downgrading your constraint on riverpod_generator: dart pub add dev:riverpod_generator:^2.6.3

File name: core/analytics_firebase/pubspec.lock

Command failed: dart pub upgrade riverpod_generator
Because core_analytics_firebase requires the Flutter SDK, version solving failed.

Flutter users should use `flutter pub` instead of `dart pub`.

File name: core/authenticator/pubspec.lock

Command failed: dart pub upgrade riverpod_generator
Because riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on analyzer ^7.0.0 and build_runner 2.4.13 depends on analyzer >=4.4.0 <7.0.0, riverpod_generator >=2.6.4 <3.0.0-dev.2 is incompatible with build_runner 2.4.13.
So, because core_authenticator depends on both build_runner 2.4.13 and riverpod_generator 2.6.4, version solving failed.


You can try one of the following suggestions to make the pubspec resolve:
* Try upgrading your constraint on build_runner: dart pub add dev:build_runner:^2.4.14
* Consider downgrading your constraint on riverpod_generator: dart pub add dev:riverpod_generator:^2.6.3

File name: core/data/pubspec.lock

Command failed: dart pub upgrade riverpod_generator
Because test 1.25.8 depends on analyzer >=5.12.0 <7.0.0 and riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on analyzer ^7.0.0, test 1.25.8 is incompatible with riverpod_generator >=2.6.4 <3.0.0-dev.2.
So, because core_data depends on both riverpod_generator 2.6.4 and test 1.25.8, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on riverpod_generator: dart pub add dev:riverpod_generator:^2.6.3

File name: core/database/pubspec.lock

Command failed: dart pub upgrade riverpod_generator
Because riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on analyzer ^7.0.0 and build_runner 2.4.13 depends on analyzer >=4.4.0 <7.0.0, riverpod_generator >=2.6.4 <3.0.0-dev.2 is incompatible with build_runner 2.4.13.
So, because core_database depends on both build_runner 2.4.13 and riverpod_generator 2.6.4, version solving failed.


You can try one of the following suggestions to make the pubspec resolve:
* Try upgrading your constraint on build_runner: dart pub add dev:build_runner:^2.4.14
* Consider downgrading your constraint on riverpod_generator: dart pub add dev:riverpod_generator:^2.6.3

File name: core/database_isar/pubspec.lock

Command failed: dart pub upgrade riverpod_generator
Because test 1.25.8 depends on analyzer >=5.12.0 <7.0.0 and riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on analyzer ^7.0.0, test 1.25.8 is incompatible with riverpod_generator >=2.6.4 <3.0.0-dev.2.
So, because core_database_isar depends on both riverpod_generator 2.6.4 and test 1.25.8, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on riverpod_generator: dart pub add dev:riverpod_generator:^2.6.3

File name: core/datastore/pubspec.lock

Command failed: dart pub upgrade riverpod_generator
Because riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on analyzer ^7.0.0 and build_runner 2.4.13 depends on analyzer >=4.4.0 <7.0.0, riverpod_generator >=2.6.4 <3.0.0-dev.2 is incompatible with build_runner 2.4.13.
So, because core_datastore depends on both build_runner 2.4.13 and riverpod_generator 2.6.4, version solving failed.


You can try one of the following suggestions to make the pubspec resolve:
* Try upgrading your constraint on build_runner: dart pub add dev:build_runner:^2.4.14
* Consider downgrading your constraint on riverpod_generator: dart pub add dev:riverpod_generator:^2.6.3

File name: core/domain/pubspec.lock

Command failed: dart pub upgrade riverpod_generator
Because test 1.25.8 depends on analyzer >=5.12.0 <7.0.0 and riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on analyzer ^7.0.0, test 1.25.8 is incompatible with riverpod_generator >=2.6.4 <3.0.0-dev.2.
So, because core_domain depends on both riverpod_generator 2.6.4 and test 1.25.8, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on riverpod_generator: dart pub add dev:riverpod_generator:^2.6.3

File name: core/model/pubspec.lock

Command failed: dart pub upgrade riverpod_generator
Because test 1.25.8 depends on analyzer >=5.12.0 <7.0.0 and riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on analyzer ^7.0.0, test 1.25.8 is incompatible with riverpod_generator >=2.6.4 <3.0.0-dev.2.
So, because core_model depends on both riverpod_generator 2.6.4 and test 1.25.8, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on riverpod_generator: dart pub add dev:riverpod_generator:^2.6.3

File name: core/network/pubspec.lock

Command failed: dart pub upgrade riverpod_generator
Because riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on source_gen ^2.0.0 and retrofit_generator 9.1.5 depends on source_gen ^1.5.0, riverpod_generator >=2.6.4 <3.0.0-dev.2 is incompatible with retrofit_generator 9.1.5.
So, because core_network depends on both retrofit_generator 9.1.5 and riverpod_generator 2.6.4, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on riverpod_generator: dart pub add dev:riverpod_generator:^2.6.3

File name: core/ui/pubspec.lock

Command failed: flutter pub upgrade riverpod_generator
Because riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on source_gen ^2.0.0 and freezed 2.5.7 depends on source_gen ^1.4.0, riverpod_generator >=2.6.4 <3.0.0-dev.2 is incompatible with freezed 2.5.7.
So, because core_ui depends on both freezed 2.5.7 and riverpod_generator 2.6.4, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on riverpod_generator: flutter pub add dev:riverpod_generator:^2.6.3
Failed to update packages.

File name: feature/feed/pubspec.lock

Command failed: flutter pub upgrade riverpod_generator
Because riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on source_gen ^2.0.0 and freezed 2.5.7 depends on source_gen ^1.4.0, riverpod_generator >=2.6.4 <3.0.0-dev.2 is incompatible with freezed 2.5.7.
So, because feature_feed depends on both freezed 2.5.7 and riverpod_generator 2.6.4, version solving failed.


You can try one of the following suggestions to make the pubspec resolve:
* Try upgrading your constraint on freezed: flutter pub add dev:freezed:^2.5.8
* Consider downgrading your constraint on riverpod_generator: flutter pub add dev:riverpod_generator:^2.6.3
Failed to update packages.

File name: feature/quest/pubspec.lock

Command failed: flutter pub upgrade riverpod_generator
Because riverpod_generator >=2.6.4 <3.0.0-dev.2 depends on source_gen ^2.0.0 and freezed 2.5.7 depends on source_gen ^1.4.0, riverpod_generator >=2.6.4 <3.0.0-dev.2 is incompatible with freezed 2.5.7.
So, because feature_quest depends on both freezed 2.5.7 and riverpod_generator 2.6.4, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on riverpod_generator: flutter pub add dev:riverpod_generator:^2.6.3
Failed to update packages.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Note

Free review on us!

CodeRabbit is offering free reviews until Wed Jan 15 2025 to showcase some of the refinements we've made.

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

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.

[github-actions]

Commands

Command	Description
/catalog	この Pull Request の Catalog を Firebase Hosting にデプロイ
/gen	コード生成コマンドを実行