Repository navigation
chore(flame_riverpod): Stop using the deprecated container.exists - #4215
Merged
Merged
Conversation
riverpod 3.5.0 deprecated `ProviderContainer.exists` in favor of the new `provider.exists` listenable. The `riverpod: ^3.0.3` constraint resolves to that release, and since CI analyzes with `fatal-infos` the deprecation fails the required `analyze` and `analyze-latest` checks on every PR. Read `provider.exists` instead, and raise the minimum `riverpod` and `flutter_riverpod` versions to 3.5.0, the release that added it.
ufrshubham
changed the title
container.existscontainer.exists
ufrshubham
enabled auto-merge (squash)
November 7, 2026 07:35
spydon
approved these changes
Nov 7, 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.
Description
riverpod 3.5.0, released on 2026-11-06, deprecated
ProviderContainer.exists. The^3.0.3constraint inflame_riverpodresolves to that release, and since CI analyzes withfatal-infos, the deprecation fails the requiredanalyzeandanalyze-latestchecks on every PR, regardless of what the PR changes.RiverpodAwareGameWidgetState.existsnow reads the newprovider.existslistenable. The publicexistsmethod offlame_riverpoddoesn't change.riverpodandflutter_riverpodversions go up to 3.5.0, because that release added the getter. Users offlame_riverpodwill need to be on 3.5.0 or newer.The deprecation message says
provider.exist, but the getter in 3.5.0 is namedprovider.exists.Tested locally on Flutter 3.47.9: the analyzer is clean across the workspace, and
melos run test:select --no-selectpasses for all 36 packages. The existingexiststests inflame_riverpodcover this change, so no new tests were added.Checklist
docsand added dartdoc comments with///.examplesordocs.Breaking Change?
Related Issues