Dependency Upgrade for `riverpod_lint` and `riverpod_generator`

[behnamsattar]

Is your feature request related to a problem? Please describe.
Yes. The current version of riverpod_lint and 'riverpod_generator' (3.0.3) depend on older versions of core Dart packages (analyzer, build, source_gen, etc.), which causes dependency resolution failures when using the latest versions of other generator packages such as go_router_builder (≥4.1.1) and graphql_codegen (≥3.0.0).
This makes it difficult to maintain up-to-date Flutter projects that rely on Riverpod and its linting utilities.

Describe the solution you'd like
Please update riverpod_lint and 'riverpod_generator' (and related packages like riverpod_analyzer_utils) to support the latest stable versions of:

• analyzer (≥ 7.4.0)
• build (≥ 4.0.0)
• source_gen (≥ 3.1.0)
• test_api (≥ 0.7.7)

Describe alternatives you've considered

• Downgrading dependencies like go_router_builder or graphql_codegen, which is not ideal as it blocks access to new features.

[rrousselGit]

Those are all supported. It's not Riverpod that's blocking. Flutter is.
I assume you're using the stable channel of Flutter. It currently is incompatible with latest analyzer versions.

[romaingyh]

I wanted to try the speed improvements of build_runner latest versions so I created a blank app on stable channel with only riverpod and build_runner and I faced a similar issue.

pubspec.yaml

environment:
  sdk: ^3.9.2

dependencies:
  flutter:
    sdk: flutter

  riverpod: ^3.0.3
  riverpod_annotation: ^3.0.3

dev_dependencies:
  flutter_test:
    sdk: flutter

  flutter_lints: ^5.0.0
  riverpod_generator: ^3.0.3
  build_runner: ^2.7.1
  custom_lint: ^0.8.0
  riverpod_lint: ^3.0.3

build_runner is constrained to 2.7.1. If I upgrade manually to 2.9.0 or 2.10.1 there is this error :

flutter pub get

Resolving dependencies...
Note: test_api is pinned to version 0.7.6 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.

The current Dart SDK version is 3.9.2.

    Because riverpod 3.0.3 depends on test ^1.0.0 and test >=1.25.9 <1.26.3 depends on analyzer >=6.0.0 <8.0.0, riverpod 3.0.3 requires analyzer >=6.0.0 <8.0.0 or test >=1.0.0 <1.25.9-∞ or >=1.26.3 <2.0.0.
(1) So, because test >=1.24.4 <1.25.9 depends on analyzer >=5.12.0 <7.0.0 and test >=1.21.6 <1.24.4 depends on analyzer >=2.0.0 <6.0.0, riverpod 3.0.3 requires analyzer >=2.0.0 <8.0.0 or test >=1.0.0 <1.21.6-∞ or >=1.26.3 <2.0.0.

    Because test >=1.16.6 <1.17.10 depends on analyzer ^1.0.0 and test >=1.17.10 <1.20.0 depends on analyzer >=1.0.0 <3.0.0, test >=1.16.6 <1.20.0 requires analyzer >=1.0.0 <3.0.0.
    And because test >=1.20.0 <1.21.2 depends on test_api 0.4.9 and test >=1.21.0 <1.21.6 depends on analyzer >=2.0.0 <5.0.0, test >=1.16.6 <1.21.6 requires analyzer >=1.0.0 <5.0.0 or test_api 0.4.9.
    And because riverpod 3.0.3 requires analyzer >=2.0.0 <8.0.0 or test >=1.0.0 <1.21.6-∞ or >=1.26.3 <2.0.0 (1), riverpod 3.0.3 requires analyzer >=1.0.0 <8.0.0 or test_api 0.4.9 or test >=1.0.0 <1.16.6-∞ or >=1.26.3 <2.0.0.
    And because riverpod_annotation 3.0.3 depends on riverpod 3.0.3 and source_gen >=4.0.1 depends on analyzer ^8.1.1, if riverpod_annotation 3.0.3 and source_gen >=4.0.1 then test_api 0.4.9 or test >=1.0.0 <1.16.6-∞ or >=1.26.3 <2.0.0.
    And because riverpod_generator 3.0.3 depends on both riverpod_annotation 3.0.3 and source_gen >=3.0.0 <5.0.0, riverpod_generator 3.0.3 requires test_api 0.4.9 or test >=1.0.0 <1.16.6-∞ or >=1.26.3 <2.0.0 or source_gen >=3.0.0 <4.0.1.
    And because no versions of riverpod_generator match >3.0.3 <4.0.0 and test >=1.26.3 depends on test_api 0.7.7, riverpod_generator ^3.0.3 requires test_api 0.4.9 or 0.7.7 or source_gen >=3.0.0 <4.0.1 or test >=1.0.0 <1.16.6.
    And because test >=1.16.0-nullsafety.19 <1.16.6 depends on test_api 0.2.19 and every version of flutter_test from sdk depends on test_api 0.7.6, if riverpod_generator ^3.0.3 and flutter_test from sdk then source_gen >=3.0.0 <4.0.1 or test >=1.0.0 <1.16.0-nullsafety.19.
    And because test >=0.12.0-beta.3 <1.16.0-nullsafety.8 doesn't support null safety and test >=1.16.0-nullsafety.8 <1.16.3 depends on web_socket_channel ^1.0.0, if riverpod_generator ^3.0.3 and flutter_test from sdk then source_gen >=3.0.0 <4.0.1 or web_socket_channel ^1.0.0.
    And because build_runner >=2.4.15 depends on web_socket_channel >=2.3.0 <4.0.0 and source_gen >=3.0.0 <4.0.1 depends on build ^3.0.0, if riverpod_generator ^3.0.3 and flutter_test from sdk and build_runner >=2.4.15 then build ^3.0.0.
    And because build_runner >=2.9.0 depends on build ^4.0.0 and temp depends on flutter_test from sdk, riverpod_generator ^3.0.3 is incompatible with build_runner >=2.9.0.
    So, because temp depends on both riverpod_generator ^3.0.3 and build_runner ^2.9.0, version solving failed.

The lower bound of "sdk: '>=1.8.0 <3.0.0'" must be 2.12.0 or higher to enable null safety.
For details, see https://dart.dev/null-safety

However I confirm it's working with beta channel (Flutter 3.37.0-0.1.pre Dart 3.10.0 (build 3.10.0-162.1.beta)
If Flutter respects it's ~3 months release cycle I think 3.37 will drop during November

[rrousselGit]

Yep like I said Flutter is the blocker :)

Hopefully this will be resolved soon. But any cases, I can't do anything here. The job's done on my side!