chore(deps): bump json_annotation, json_serializable, mockito and build_runner

[dependabot]

Bumps json_annotation, json_serializable, mockito and build_runner. These dependencies needed to be updated together.
Updates json_annotation from 4.9.0 to 4.12.0

Release notes

Sourced from json_annotation's releases.

package:json_annotation v4.12.0

• Add JsonKey.explicitJsonNullWhenNonNullField for PATCH-style tri-state JSON fields (omit key vs explicit null vs value).

package:json_annotation v4.11.0

• Add JsonSerializable.dateTimeUtc configuration option. (#1371)

package:json_annotation v4.10.0

• Support JsonKey annotation on constructor parameters.
• Add JsonSerializable(createJsonSchema: true).
• Require meta: ^1.16.0
• Require sdk: ^3.9.0

Commits

• 61e7b87 Add JsonKey.explicitJsonNullWhenNonNullField for PATCH tri-state JSON (#1574)
• 62e16d8 Bump the dependencies group with 2 updates (#1572)
• c6cdfcf Update analyzer to latest, prepare v6.13.2 (#1571)
• fba9479 Bump the dependencies group with 3 updates (#1568)
• da67f42 allow pkg:analyzer latest, prepare v6.13.1 (#1566)
• 8b781ac Improve error message when generating code for Record types with unsupported ...
• 6b711e3 Improve error messages when typeToCode throws an exception (#1450)
• 5d5feca isSynthetic is removed in Analyzer 11 (#1564)
• c61a809 Bump actions/stale from 10.1.1 to 10.2.0 in the dependencies group (#1563)
• 2b03869 Prepare for release (#1562)
• Additional commits viewable in compare view

Updates json_serializable from 6.9.5 to 6.14.1

Release notes

Sourced from json_serializable's releases.

package:json_serializable v6.14.1

• Require analyzer: '>=10.0.0 <15.0.0'

package:json_serializable v6.14.0

• Support JsonKey.explicitJsonNullWhenNonNullField for PATCH-style tri-state JSON fields: distinguish omitted keys from explicit null in fromJson and emit explicit JSON null in toJson when the Dart field is non-null.
• Require json_annotation: '>=4.12.0 <4.13.0'

package:json_serializable v6.13.2

• Require analyzer: '>=10.0.0 <14.0.0'

package:json_serializable v6.13.1

• Improve error message when generating code for Record types with unsupported fields. (#1559)
• Require analyzer: '>=10.0.0 <13.0.0'
• Require build: ^4.0.4
• Require dart_style: ^3.1.4
• Require source_gen: ^4.1.2
• Require source_helper: ^1.3.10

package:json_serializable v6.13.0

• Fix schema generation for many different types of fields. (#1549)
• Support JsonSerializable.dateTimeUtc configuration option. (#1371)
• Remove json_schema from dependencies (it is only used in tests).

package:json_serializable v6.12.0

• Support JsonKey annotation on constructor parameters.
• Add support for JsonSerializable(createJsonSchema: true).

package:json_serializable v6.11.4

• Allow analyzer: >=9.0.0 <11.0.0

package:json_serializable v6.11.3

• Require analyzer: ^9.0.0
• Require build: ^4.0.3
• Require build_config: ^1.2.0
• Require dart_style: ^3.1.3
• Require sdk: ^3.9.0
• Require source_gen: ^4.1.1
• Require source_helper: ^1.3.9

package:json_serializable v6.11.2

• Allow run_only_if_triggered to be specified in build.yaml to turn on the build_runner triggers heuristic.
• Skip warning about annotations on both constructor and field if the values match.

... (truncated)

Commits

• c727bb9 chore(deps): support analyzer <15.0.0 (#1584)
• eaad5f6 Bump the dependencies group with 2 updates (#1579)
• 5a1856a Bump the dependencies group with 2 updates (#1576)
• 61e7b87 Add JsonKey.explicitJsonNullWhenNonNullField for PATCH tri-state JSON (#1574)
• 62e16d8 Bump the dependencies group with 2 updates (#1572)
• c6cdfcf Update analyzer to latest, prepare v6.13.2 (#1571)
• fba9479 Bump the dependencies group with 3 updates (#1568)
• da67f42 allow pkg:analyzer latest, prepare v6.13.1 (#1566)
• 8b781ac Improve error message when generating code for Record types with unsupported ...
• 6b711e3 Improve error messages when typeToCode throws an exception (#1450)
• Additional commits viewable in compare view

Updates mockito from 5.4.6 to 5.7.0

Release notes

Sourced from mockito's releases.

package:mockito v5.7.0

• Handle JS interop extension types and provide dummy values for them. #4498

package:mockito v5.6.5

• Require analyzer 13.0.0.

package:mockito v5.6.4

• Allow analyzer 11.0.0 and 12.0.0.
• Move to dart-lang/build monorepo.

Commits

• See full diff in compare view

Updates build_runner from 2.5.4 to 2.15.1

Release notes

Sourced from build_runner's releases.

package:build_runner v2.15.1

• Pass Dart SDK --packages arg to builder compiles, so they can be compiled with different packages to the current version solve.
• More efficient watching for file changes in workspaces and other setups with nested packages.
• Support builders with no declared outputs. They can't output anything, but they can do processing, write log messages and choose whether to fail the build.
• Mention in command usage that --define values are parsed as JSON with a fallback.
• Performance: reduce size of serialized build state when there are optional outputs that are not written.
• Bug fix: handle errors from post process builders in previous runs without crashing.
• Bug fix: fix dart run build_runner test to correctly pass arguments after -- to the test process.
• Bug fix: fix crash if a resolved Dart source contains invalid utf8.
• Bug fix: fix incorrect output when builder code changes during builder compile.
• Bug fix: do a clean build when switching between a workspace build and a package build, as incremental builds were sometimes incorrect.
• Require Dart 3.8.0.

package:build_runner v2.15.0

• Remove --low-resources-mode as default memory usage has been improved. If you have problems with RAM usage please file an issue.
• Remove --log-performance and --track-performance. File an issue if you have performance measurement needs not covered by the newer --dart-aot-perf.
• Removed options can still be passed, they will be ignored with a warning.
• Bug fix: fix crash during logging if an asset path is an invalid URI.
• Bug fix: with --workspace the global options affecting build order were read from the wrong package. They are now read from build.yaml in the workspace root, like other global options.
• Allow analyzer 13.0.0.

package:build_runner v2.14.1

• Bug fix: fix crash if a package used to belong to a workspace but was removed from the workspace leaving a stale workspace.ref file.
• Bug fix: the watch command now always does one build before exiting due to a request from another build_runner process. Fix crashes related to request before build start.

package:build_runner v2.14.0

• Performance: further improvements to management of files for analysis for 2x faster incremental builds.
• Performance: default to AOT compilation for commands other than run. This costs more initial startup time but gives faster builds afterwards. Fall back to JIT if the compile fails due to use of dart:mirrors. Use the --force-jit flag if you want the old default JIT builder compile. Use the --force-aot flag to turn off the fallback to JIT compile.

... (truncated)

Commits

• 565856b Release build 4.0.7, build_runner 3.15.1. (#5010)
• 76f0f89 Fix workspace vs package build config conflict (#5008)
• 8921c3f Formatting changes due to latest dev SDK. (#5007)
• e999ea4 Fix incorrect build due to racy builder changes. (#4988)
• d2a2f4f Bump SDK upper bounds. (#5006)
• a72038d Set flattenBuild in passed ReaderWriter. (#5004)
• ea0cf6b fix(build_daemon): reject cross-origin WebSocket handshakes (CSWSH) (#4992)
• ae52e61 Use BuiltList.of instead of BuiltList.from. (#5003)
• a8e949c Fix trigger evaluation reading ungenerated parts. (#5000)
• 39353ef Bump actions/cache from 5.0.5 to 6.1.0 in the github-actions group (#5002)
• Additional commits viewable in compare view

[devin-ai-integration]

Devin Review found 2 potential issues.

View 1 additional finding in Devin Review.

[devin-ai-integration]

🟡 Code-generation dependency upgrade drops support for the oldest Dart version the package claims to support

The upper cap that kept the JSON code generator usable on Dart 3.6 is removed (json_serializable: ^6.14.1 at pubspec.yaml:66), while the package still advertises support down to Dart 3.6, so anyone on Dart 3.6–3.8 can no longer install the project's dependencies.
Impact: Contributors and CI setups running the minimum supported Dart/Flutter version will fail at dependency resolution instead of being able to build or test.

Version constraint conflict between environment and dev dependencies

pubspec.yaml:26 declares sdk: ">=3.6.0 <4.0.0". The previous constraint json_serializable: ">=6.9.5 <6.10.0" was added deliberately in commit 0733150 ("chore(deps): cap json_serializable for Dart 3.6 support"). json_serializable 6.14.1 requires sdk: ^3.9.0 (and pulls analyzer 13 / build_runner 2.15.1, which requires Dart 3.8+ per the release notes in the PR description), so on a Dart 3.6/3.7/3.8 SDK flutter pub get cannot resolve: the locked 6.14.1 is rejected and no version in ^6.14.1 is compatible.

Either restore an upper cap compatible with Dart 3.6, or raise the declared environment: sdk lower bound (and the AGENTS.md "Requires Dart >= 3.6" statement) in the same change.

Prompt for agents

pubspec.yaml declares environment sdk ">=3.6.0 <4.0.0", and the json_serializable constraint was previously pinned to ">=6.9.5 <6.10.0" intentionally (commit 0733150 'cap json_serializable for Dart 3.6 support'). This PR changes it to ^6.14.1; json_serializable 6.14.1 requires Dart ^3.9.0 and build_runner 2.15.1 requires Dart 3.8+, so dependency resolution fails on the minimum SDK the package claims to support. Decide whether to keep the cap (staying Dart 3.6-compatible) or to bump the declared minimum SDK in pubspec.yaml and the corresponding documentation (AGENTS.md, README) consistently.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🟡 Change is missing the required release note file

No release-note file is added under .changes/ for this dependency bump, which the repository requires for every pull request, so the change fails the project's release-notes check.
Impact: The pull request cannot pass required checks and the change is absent from generated release notes.

Repository rule

AGENTS.md ("Releases") states: "Every PR needs a changeset file in .changes/ (format: patch|minor|major type=\"fixed|added|changed|...\" \"description\"); CI checks for it". This commit only touches pubspec.yaml and pubspec.lock.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 4 additional findings in Devin Review.

[devin-ai-integration]

🔴 Dependency bump breaks the SDK versions the package still claims to support

The code-generation dependency is raised to a release line that requires a much newer Dart (json_serializable: ^6.14.1 at pubspec.yaml:66) while the package still advertises support for older Dart versions, so anyone on those older versions can no longer fetch dependencies or build this package.
Impact: Contributors and CI running the older supported Dart/Flutter versions get a dependency resolution failure instead of a working build.

Reverts the deliberate Dart 3.6 compatibility cap added in #1070

pubspec.yaml:26 still declares sdk: ">=3.6.0 <4.0.0" / flutter: ">=3.27.0". The previous constraint ">=6.9.5 <6.10.0" was introduced intentionally in commit 0733150 ("chore(deps): cap json_serializable for Dart 3.6 support") because json_serializable 6.10.0+ requires Dart 3.8 and generates null-aware collection elements that fail codegen/analysis at the declared SDK lower bound. json_serializable 6.14.x requires sdk: ^3.9.0 (and pulls analyzer 13, build 4.x, build_runner 2.15.1 which requires Dart 3.8+), all of which are now pinned in pubspec.lock (e.g. analyzer 13.0.0, build_runner 2.15.1, json_annotation 4.12.0, which itself requires sdk ^3.9.0).

Either the environment lower bound must be raised to ^3.9.0 (a user-facing change needing a changeset), or the cap must be kept.

Prompt for agents

pubspec.yaml declares environment sdk ">=3.6.0 <4.0.0", but this PR raises json_serializable to ^6.14.1, whose release line requires Dart ^3.9.0 (and drags in analyzer 13 / build 4.x / build_runner 2.15.1, which require Dart 3.8+). The previous cap ">=6.9.5 <6.10.0" was added deliberately in commit 0733150 precisely because newer json_serializable breaks `dart run build_runner build` and analysis at the declared SDK lower bound. Decide between (a) restoring the cap so the package keeps supporting Dart 3.6, or (b) raising the environment sdk/flutter lower bounds to match the new toolchain requirement and adding the corresponding changeset entry in .changes/ since that is a user-facing compatibility change. Also verify the committed *.g.dart files regenerate cleanly under whichever combination is chosen.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[github-actions]

Warning

No changeset found

If this PR includes user-facing changes, please add a changeset file in .changes/

Format: level type="kind" "description"

patch type="fixed" "Fix audio frame generation"
minor type="added" "Add support for custom audio processing"
major type="changed" "Breaking: Rename Room.connect() to Room.join()"

[hiroshihorie]

Superseded by #1170, which unpinned json_serializable to 6.14.x at the pubspec level (now possible with the Dart 3.10 floor) and refreshed the same lockfile group including mockito 5.7.0 and analyzer 13.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.