chore(deps): bump json_annotation, json_serializable, mockito and build_runner - #1143
chore(deps): bump json_annotation, json_serializable, mockito and build_runner#1143dependabot[bot] wants to merge 1 commit into
Conversation
…ld_runner Bumps [json_annotation](https://github.com/google/json_serializable.dart), [json_serializable](https://github.com/google/json_serializable.dart), [mockito](https://github.com/dart-lang/build/tree/master/builder_pkgs) and [build_runner](https://github.com/dart-lang/build). These dependencies needed to be updated together. Updates `json_annotation` from 4.9.0 to 4.12.0 - [Release notes](https://github.com/google/json_serializable.dart/releases) - [Commits](google/json_serializable.dart@json_annotation-v4.9.0...json_annotation-v4.12.0) Updates `json_serializable` from 6.9.5 to 6.14.1 - [Release notes](https://github.com/google/json_serializable.dart/releases) - [Commits](google/json_serializable.dart@json_serializable-v6.9.5...json_serializable-v6.14.1) Updates `mockito` from 5.4.6 to 5.7.0 - [Release notes](https://github.com/dart-lang/build/releases) - [Commits](https://github.com/dart-lang/build/commits/mockito-v5.7.0/builder_pkgs) Updates `build_runner` from 2.5.4 to 2.15.1 - [Release notes](https://github.com/dart-lang/build/releases) - [Commits](dart-lang/build@build_runner-v2.5.4...build_runner-v2.15.1) --- updated-dependencies: - dependency-name: json_annotation dependency-version: 4.12.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: json_serializable dependency-version: 6.14.1 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: mockito dependency-version: 5.7.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: build_runner dependency-version: 2.15.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
| yaml: ^3.1.2 | ||
| build_runner: ^2.4.13 | ||
| json_serializable: ">=6.9.5 <6.10.0" | ||
| json_serializable: ^6.14.1 |
There was a problem hiding this comment.
🟡 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.
| yaml: ^3.1.2 | ||
| build_runner: ^2.4.13 | ||
| json_serializable: ">=6.9.5 <6.10.0" | ||
| json_serializable: ^6.14.1 |
There was a problem hiding this comment.
🟡 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.
Bumps json_annotation, json_serializable, mockito and build_runner. These dependencies needed to be updated together.
Updates
json_annotationfrom 4.9.0 to 4.12.0Release notes
Sourced from json_annotation's releases.
Commits
61e7b87Add JsonKey.explicitJsonNullWhenNonNullField for PATCH tri-state JSON (#1574)62e16d8Bump the dependencies group with 2 updates (#1572)c6cdfcfUpdate analyzer to latest, prepare v6.13.2 (#1571)fba9479Bump the dependencies group with 3 updates (#1568)da67f42allow pkg:analyzer latest, prepare v6.13.1 (#1566)8b781acImprove error message when generating code for Record types with unsupported ...6b711e3Improve error messages when typeToCode throws an exception (#1450)5d5fecaisSynthetic is removed in Analyzer 11 (#1564)c61a809Bump actions/stale from 10.1.1 to 10.2.0 in the dependencies group (#1563)2b03869Prepare for release (#1562)Updates
json_serializablefrom 6.9.5 to 6.14.1Release notes
Sourced from json_serializable's releases.
... (truncated)
Commits
c727bb9chore(deps): support analyzer <15.0.0 (#1584)eaad5f6Bump the dependencies group with 2 updates (#1579)5a1856aBump the dependencies group with 2 updates (#1576)61e7b87Add JsonKey.explicitJsonNullWhenNonNullField for PATCH tri-state JSON (#1574)62e16d8Bump the dependencies group with 2 updates (#1572)c6cdfcfUpdate analyzer to latest, prepare v6.13.2 (#1571)fba9479Bump the dependencies group with 3 updates (#1568)da67f42allow pkg:analyzer latest, prepare v6.13.1 (#1566)8b781acImprove error message when generating code for Record types with unsupported ...6b711e3Improve error messages when typeToCode throws an exception (#1450)Updates
mockitofrom 5.4.6 to 5.7.0Release notes
Sourced from mockito's releases.
Commits
Updates
build_runnerfrom 2.5.4 to 2.15.1Release notes
Sourced from build_runner's releases.
... (truncated)
Commits
565856bRelease build 4.0.7, build_runner 3.15.1. (#5010)76f0f89Fix workspace vs package build config conflict (#5008)8921c3fFormatting changes due to latest dev SDK. (#5007)e999ea4Fix incorrect build due to racy builder changes. (#4988)d2a2f4fBump SDK upper bounds. (#5006)a72038dSet flattenBuild in passed ReaderWriter. (#5004)ea0cf6bfix(build_daemon): reject cross-origin WebSocket handshakes (CSWSH) (#4992)ae52e61Use BuiltList.of instead of BuiltList.from. (#5003)a8e949cFix trigger evaluation reading ungenerated parts. (#5000)39353efBump actions/cache from 5.0.5 to 6.1.0 in the github-actions group (#5002)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)