Repository navigation
[leancode_force_update] Upgrade contracts dependencies - #559
Merged
PiotrRogulski merged 4 commits intoAug 10, 2026
Merged
Conversation
Bump `leancode_contracts` to `^0.10.0` and `leancode_contracts_generator` to `^0.19.0`, which moves serialization generation from `json_serializable` to the generator's own `contracts_serializable` builder. `leancode_lint` has to go up to `^19.0.0` as well, since the new generator requires `analyzer` v8+. Also bump the `dotnet-contracts-generate` tool to `4.1.0` and regenerate the contracts — the only change in the output is the generator header in `contracts.g.dart`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CwSEMS3JeqqcupWaZcS18h
Since `leancode_contracts_generator` v0.19.0 generates serialization with its own builder, the `json_serializable` builder is a no-op here. Regenerating without it leaves `contracts.g.dart` unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CwSEMS3JeqqcupWaZcS18h
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CwSEMS3JeqqcupWaZcS18h
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CwSEMS3JeqqcupWaZcS18h
github-actions
Bot
added
the
p: leancode_force_update
PiotrRogulski
marked this pull request as ready for review
August 9, 2026 10:51
Member
Author
|
pana reports 150/160 because we don't support |
Komoszek
approved these changes
Aug 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrades the contracts toolchain in
leancode_force_updateand regenerates the contracts.Changes
leancode_contracts^0.9.0→^0.10.0leancode_contracts_generator^0.18.0→^0.19.0dotnet-contracts-generate(.config/dotnet-tools.json)4.0.0→4.1.0leancode_lint^17.0.0→^19.0.0— forced by the above: lint 17/18 pinanalyzer ^7.3.0while the new generator needsanalyzer >=8.1.1, so version solving failed otherwise. 19.0.x is the lowest version that resolves while keeping the package'ssdk: >=3.10.0floor (lint ≥20 would require bumping the SDK/Flutter constraints and the CI matrix).json_serializabledev dependency — generator v0.19.0 generates serialization with its owncontracts_serializablebuilder, so thejson_serializablebuilder had become a no-op here. It remains in the lockfile as a transitive dependency of the generator.build_runnerstays, since it drives the new builder.1.0.4-alpha(1.0.3-alphais already published), with a CHANGELOG entry.Leancode.ForceUpdate.Contractsis left at10.0.2860— already the newest published version.Regenerated output
contracts.dartis unchanged. The only change incontracts.g.dartis the generator header:The
fromJson/toJsonbodies are byte-identical, both across the generator upgrade and across thedotnet-contracts-generatebump.Verification
Ran locally against Flutter 3.44.9 stable and .NET SDK 8:
flutter analyze— no issuesflutter test— 8/8 passingflutter pub publish --dry-run— clean apart from the usual "not an incremental update" hint that the-alphaversioning scheme has always producedGenerated by Claude Code