chore(deps): update flutter

[renovate]

This PR contains the following updates:

Package	Update	Change
dart (source)	minor	3.5.4 -> 3.6.0
flutter (source)	minor	3.24.5 -> 3.27.1

---

Warning

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

---

Release Notes

dart-lang/sdk (dart)

v3.6.0

Compare Source

Language

Dart 3.6 adds digit separators to the language. To use them, set your
package's [SDK constraint][language version] lower bound to 3.6 or greater
(sdk: '^3.6.0').

Digit separators

Digits in number literals (decimal integer literals, double literals,
scientific notation literals, and hexadecimal literals) can now include
underscores between digits, as "digit separators." The separators do not change
the value of a literal, but can serve to make the number more readable.

100__000_000__000_000__000_000  // one hundred million million millions!
0x4000_0000_0000_0000
0.000_000_000_01
0x00_14_22_01_23_45  // MAC address

Separators are not allowed at the start of a number (this would be parsed as an
identifier), at the end of a number, or adjacent to another character in a
number, like ., x, or the e in scientific notation.

• Breaking Change #​56065: The context used by the compiler and analyzer
  to perform type inference on the operand of a throw expression has been
  changed from the "unknown type" to Object. This makes the type system more
  self-consistent, because it reflects the fact that it's not legal to throw
  null. This change is not expected to make any difference in practice.

Libraries

dart:io

• Breaking Change #​52444: Removed the Platform() constructor, which
  has been deprecated since Dart 3.1.

• Breaking Change #​53618: HttpClient now responds to a redirect
  that is missing a "Location" header by throwing RedirectException, instead
  of StateError.

dart:js_interop

• Added constructors for JSArrayBuffer, JSDataView, and concrete typed array
  types e.g. JSInt8Array.
• Added length and []/[]= operators to JSArray.
• Added toJSCaptureThis so this is passed in from JavaScript to the
  callback as the first parameter.
• Added a static from method on JSArray to create a JSArray from a given
  JavaScript iterable or array-like object.

Tools

CFE

• Breaking Change #​56466: The implementation of the UP and
  DOWN algorithms in the CFE are changed to match the specification
  and the corresponding implementations in the Analyzer. The upper and
  lower closures of type schemas are now computed just before they are
  passed into the subtype testing procedure instead of at the very
  beginning of the UP and DOWN algorithms.

Dart format

• Preserve type parameters on old-style function-typed formals that also use
  this. or super..
• Correctly format imports with both as and if clauses.

Wasm compiler (dart2wasm)

• The condition dart.library.js is now false on conditional imports in
  dart2wasm. Note that it was already a static error to import dart:js
  directly (see #​55266).

Pub

• Support for workspaces. This allows you to develop and resolve multiple
  packages from the same repo together. See https://dart.dev/go/pub-workspaces
  for more info.

• New command dart pub bump. Increments the version number of the current
  package.

  For example: dart pub bump minor will change the version from 1.2.3 to
  1.3.0.

• New validation: dart pub publish will warn if your git status is not
  clean.

• New flag dart pub upgrade --unlock-transitive.

• dart pub upgrade --unlock-transitive pkg, will unlock and upgrade all the
  dependencies of pkg instead of just pkg.

Analyzer

• Add the [use_truncating_division][use_truncating_division] lint rule.
• Add the experimental [omit_obvious_local_variable_types][omit_obvious_local_variable_types] lint rule.
• Add the experimental [specify_nonobvious_local_variable_types][specify_nonobvious_local_variable_types] lint rule.
• Add the experimental [avoid_futureor_void][avoid_futureor_void] lint rule.
• Add quick fixes for more than 14 diagnostics.
• Add new assists: "add digit separators", "remove digit separators", and
  "invert conditional expression".

flutter/flutter (flutter)

v3.27.1

Compare Source

v3.27.0

Compare Source

Initial stable release.

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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/catalog/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter from sdk is incompatible with core_common from path.
And because every version of feature_settings from path depends on core_common from path, flutter from sdk is incompatible with feature_settings from path.
So, because app_catalog depends on both feature_settings from path and flutter from sdk, version solving failed.
Failed to update packages.

File name: app/mobile/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter_localizations from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter_localizations from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter_localizations from sdk is incompatible with core_common from path.
So, because app_mobile depends on both core_common from path and flutter_localizations from sdk, version solving failed.
Failed to update packages.

File name: core/analytics/pubspec.lock

Command failed: dart pub get --no-precompile
Because every version of core_common from path depends on collection 1.18.0 and analyzer >=6.8.0 depends on collection ^1.19.0, core_common from path is incompatible with analyzer >=6.8.0.
And because no versions of analyzer match >6.7.0 <6.8.0 and riverpod_generator 2.6.3 depends on analyzer ^6.7.0, if core_common from path and riverpod_generator 2.6.3 then analyzer 6.7.0.
And because analyzer 6.7.0 depends on macros >=0.1.2-main.3 <0.1.3 and no versions of macros match >0.1.2-main.4 <0.1.3, if core_common from path and riverpod_generator 2.6.3 then macros >=0.1.2-main.3 <=0.1.2-main.4.
And because macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk which doesn't match any versions, if core_common from path and riverpod_generator 2.6.3 then macros 0.1.2-main.4.
And because macros 0.1.2-main.4 depends on _macros 0.3.2 from sdk which doesn't match any versions, core_common from path is incompatible with riverpod_generator 2.6.3.
So, because core_analytics depends on both core_common from path and riverpod_generator 2.6.3, 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.4.0

File name: core/analytics_firebase/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because firebase_analytics 11.3.5 depends on flutter from sdk which depends on collection 1.19.0, firebase_analytics 11.3.5 requires collection 1.19.0.
And because every version of core_common from path depends on collection 1.18.0, firebase_analytics 11.3.5 is incompatible with core_common from path.
So, because core_analytics_firebase depends on both core_common from path and firebase_analytics 11.3.5, version solving failed.
Failed to update packages.

File name: core/authenticator/pubspec.lock

Command failed: dart pub get --no-precompile
Because every version of core_common from path depends on collection 1.18.0 and analyzer >=6.8.0 depends on collection ^1.19.0, core_common from path is incompatible with analyzer >=6.8.0.
And because no versions of analyzer match >6.7.0 <6.8.0 and riverpod_generator 2.6.3 depends on analyzer ^6.7.0, if core_common from path and riverpod_generator 2.6.3 then analyzer 6.7.0.
And because analyzer 6.7.0 depends on macros >=0.1.2-main.3 <0.1.3 and no versions of macros match >0.1.2-main.4 <0.1.3, if core_common from path and riverpod_generator 2.6.3 then macros >=0.1.2-main.3 <=0.1.2-main.4.
And because macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk which doesn't match any versions, if core_common from path and riverpod_generator 2.6.3 then macros 0.1.2-main.4.
And because macros 0.1.2-main.4 depends on _macros 0.3.2 from sdk which doesn't match any versions, core_common from path is incompatible with riverpod_generator 2.6.3.
So, because core_authenticator depends on both core_common from path and riverpod_generator 2.6.3, 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.4.0

File name: core/data/pubspec.lock

Command failed: dart pub get --no-precompile
Because every version of core_common from path depends on collection 1.18.0 and analyzer >=6.8.0 depends on collection ^1.19.0, core_common from path is incompatible with analyzer >=6.8.0.
And because no versions of analyzer match >6.7.0 <6.8.0 and riverpod_generator 2.6.3 depends on analyzer ^6.7.0, if core_common from path and riverpod_generator 2.6.3 then analyzer 6.7.0.
And because analyzer 6.7.0 depends on macros >=0.1.2-main.3 <0.1.3 and no versions of macros match >0.1.2-main.4 <0.1.3, if core_common from path and riverpod_generator 2.6.3 then macros >=0.1.2-main.3 <=0.1.2-main.4.
And because macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk which doesn't match any versions, if core_common from path and riverpod_generator 2.6.3 then macros 0.1.2-main.4.
And because macros 0.1.2-main.4 depends on _macros 0.3.2 from sdk which doesn't match any versions, core_common from path is incompatible with riverpod_generator 2.6.3.
So, because core_data depends on both core_common from path and riverpod_generator 2.6.3, 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.4.0

File name: core/database/pubspec.lock

Command failed: dart pub get --no-precompile
Because every version of core_common from path depends on collection 1.18.0 and analyzer >=6.8.0 depends on collection ^1.19.0, core_common from path is incompatible with analyzer >=6.8.0.
And because no versions of analyzer match >6.7.0 <6.8.0 and riverpod_generator 2.6.3 depends on analyzer ^6.7.0, if core_common from path and riverpod_generator 2.6.3 then analyzer 6.7.0.
And because analyzer 6.7.0 depends on macros >=0.1.2-main.3 <0.1.3 and no versions of macros match >0.1.2-main.4 <0.1.3, if core_common from path and riverpod_generator 2.6.3 then macros >=0.1.2-main.3 <=0.1.2-main.4.
And because macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk which doesn't match any versions, if core_common from path and riverpod_generator 2.6.3 then macros 0.1.2-main.4.
And because macros 0.1.2-main.4 depends on _macros 0.3.2 from sdk which doesn't match any versions, core_common from path is incompatible with riverpod_generator 2.6.3.
So, because core_database depends on both core_common from path and riverpod_generator 2.6.3, 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.4.0

File name: core/database_isar/pubspec.lock

Command failed: dart pub get --no-precompile
Because every version of core_common from path depends on collection 1.18.0 and analyzer >=6.8.0 depends on collection ^1.19.0, core_common from path is incompatible with analyzer >=6.8.0.
And because no versions of analyzer match >6.7.0 <6.8.0 and riverpod_generator 2.6.3 depends on analyzer ^6.7.0, if core_common from path and riverpod_generator 2.6.3 then analyzer 6.7.0.
And because analyzer 6.7.0 depends on macros >=0.1.2-main.3 <0.1.3 and no versions of macros match >0.1.2-main.4 <0.1.3, if core_common from path and riverpod_generator 2.6.3 then macros >=0.1.2-main.3 <=0.1.2-main.4.
And because macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk which doesn't match any versions, if core_common from path and riverpod_generator 2.6.3 then macros 0.1.2-main.4.
And because macros 0.1.2-main.4 depends on _macros 0.3.2 from sdk which doesn't match any versions, core_common from path is incompatible with riverpod_generator 2.6.3.
So, because core_database_isar depends on both core_common from path and riverpod_generator 2.6.3, 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.4.0

File name: core/datastore/pubspec.lock

Command failed: dart pub get --no-precompile
Because every version of core_common from path depends on collection 1.18.0 and analyzer >=6.8.0 depends on collection ^1.19.0, core_common from path is incompatible with analyzer >=6.8.0.
And because no versions of analyzer match >6.7.0 <6.8.0 and riverpod_generator 2.6.3 depends on analyzer ^6.7.0, if core_common from path and riverpod_generator 2.6.3 then analyzer 6.7.0.
And because analyzer 6.7.0 depends on macros >=0.1.2-main.3 <0.1.3 and no versions of macros match >0.1.2-main.4 <0.1.3, if core_common from path and riverpod_generator 2.6.3 then macros >=0.1.2-main.3 <=0.1.2-main.4.
And because macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk which doesn't match any versions, if core_common from path and riverpod_generator 2.6.3 then macros 0.1.2-main.4.
And because macros 0.1.2-main.4 depends on _macros 0.3.2 from sdk which doesn't match any versions, core_common from path is incompatible with riverpod_generator 2.6.3.
So, because core_datastore depends on both core_common from path and riverpod_generator 2.6.3, 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.4.0

File name: core/designsystem/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter_test from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter_test from sdk is incompatible with core_common from path.
So, because core_designsystem depends on both core_common from path and flutter_test from sdk, version solving failed.
Failed to update packages.

File name: core/domain/pubspec.lock

Command failed: dart pub get --no-precompile
Because every version of core_common from path depends on collection 1.18.0 and analyzer >=6.8.0 depends on collection ^1.19.0, core_common from path is incompatible with analyzer >=6.8.0.
And because no versions of analyzer match >6.7.0 <6.8.0 and riverpod_generator 2.6.3 depends on analyzer ^6.7.0, if core_common from path and riverpod_generator 2.6.3 then analyzer 6.7.0.
And because analyzer 6.7.0 depends on macros >=0.1.2-main.3 <0.1.3 and no versions of macros match >0.1.2-main.4 <0.1.3, if core_common from path and riverpod_generator 2.6.3 then macros >=0.1.2-main.3 <=0.1.2-main.4.
And because macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk which doesn't match any versions, if core_common from path and riverpod_generator 2.6.3 then macros 0.1.2-main.4.
And because macros 0.1.2-main.4 depends on _macros 0.3.2 from sdk which doesn't match any versions, core_common from path is incompatible with riverpod_generator 2.6.3.
So, because core_domain depends on both core_common from path and riverpod_generator 2.6.3, 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.4.0

File name: core/model/pubspec.lock

Command failed: dart pub get --no-precompile
Because every version of core_common from path depends on collection 1.18.0 and analyzer >=6.8.0 depends on collection ^1.19.0, core_common from path is incompatible with analyzer >=6.8.0.
And because no versions of analyzer match >6.7.0 <6.8.0 and riverpod_generator 2.6.3 depends on analyzer ^6.7.0, if core_common from path and riverpod_generator 2.6.3 then analyzer 6.7.0.
And because analyzer 6.7.0 depends on macros >=0.1.2-main.3 <0.1.3 and no versions of macros match >0.1.2-main.4 <0.1.3, if core_common from path and riverpod_generator 2.6.3 then macros >=0.1.2-main.3 <=0.1.2-main.4.
And because macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk which doesn't match any versions, if core_common from path and riverpod_generator 2.6.3 then macros 0.1.2-main.4.
And because macros 0.1.2-main.4 depends on _macros 0.3.2 from sdk which doesn't match any versions, core_common from path is incompatible with riverpod_generator 2.6.3.
So, because core_model depends on both core_common from path and riverpod_generator 2.6.3, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Try an upgrade of your constraints: dart pub upgrade --major-versions

File name: core/network/pubspec.lock

Command failed: dart pub get --no-precompile
Because every version of core_common from path depends on collection 1.18.0 and analyzer >=6.8.0 depends on collection ^1.19.0, core_common from path is incompatible with analyzer >=6.8.0.
And because no versions of analyzer match >6.7.0 <6.8.0 and riverpod_generator 2.6.3 depends on analyzer ^6.7.0, if core_common from path and riverpod_generator 2.6.3 then analyzer 6.7.0.
And because analyzer 6.7.0 depends on macros >=0.1.2-main.3 <0.1.3 and no versions of macros match >0.1.2-main.4 <0.1.3, if core_common from path and riverpod_generator 2.6.3 then macros >=0.1.2-main.3 <=0.1.2-main.4.
And because macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk which doesn't match any versions, if core_common from path and riverpod_generator 2.6.3 then macros 0.1.2-main.4.
And because macros 0.1.2-main.4 depends on _macros 0.3.2 from sdk which doesn't match any versions, core_common from path is incompatible with riverpod_generator 2.6.3.
So, because core_network depends on both core_common from path and riverpod_generator 2.6.3, version solving failed.

File name: core/ui/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter_test from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter_test from sdk is incompatible with core_common from path.
So, because core_ui depends on both core_common from path and flutter_test from sdk, version solving failed.
Failed to update packages.

File name: feature/auth/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter_test from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter_test from sdk is incompatible with core_common from path.
So, because feature_auth depends on both core_common from path and flutter_test from sdk, version solving failed.
Failed to update packages.

File name: feature/debug/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter_test from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter_test from sdk is incompatible with core_common from path.
So, because feature_debug depends on both core_common from path and flutter_test from sdk, version solving failed.
Failed to update packages.

File name: feature/feed/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter_test from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter_test from sdk is incompatible with core_common from path.
So, because feature_feed depends on both core_common from path and flutter_test from sdk, version solving failed.
Failed to update packages.

File name: feature/home/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter_test from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter_test from sdk is incompatible with core_common from path.
So, because feature_home depends on both core_common from path and flutter_test from sdk, version solving failed.
Failed to update packages.

File name: feature/onboarding/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter_localizations from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter_localizations from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter_localizations from sdk is incompatible with core_common from path.
So, because feature_onboarding depends on both core_common from path and flutter_localizations from sdk, version solving failed.
Failed to update packages.

File name: feature/quest/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter_test from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter_test from sdk is incompatible with core_common from path.
So, because feature_quest depends on both core_common from path and flutter_test from sdk, version solving failed.
Failed to update packages.

File name: feature/settings/pubspec.lock

Command failed: flutter pub get --no-precompile
Note: collection is pinned to version 1.19.0 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because every version of flutter_test from sdk depends on collection 1.19.0 and every version of core_common from path depends on collection 1.18.0, flutter_test from sdk is incompatible with core_common from path.
So, because feature_settings depends on both core_common from path and flutter_test from sdk, version solving failed.
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.

---

🪧 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	コード生成コマンドを実行