| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Raise flutter_cache_manager to ^3.4.5, material_ui to ^1.3.0, octo_image to ^2.1.1 and mocktail to ^1.0.5. material_ui 1.3.0 is the newest release that keeps the Dart ^3.12 / Flutter >=3.44 floor. Bring the example along: flutter_lints ^6.0.0, flutter_blurhash ^0.9.1, baseflow_plugin_template ^2.2.1, and an SDK constraint that matches the package it depends on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Raising the example's SDK constraint to ^3.12.0 selects the tall style formatter, which failed the Format check on example/lib/main.dart. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # cached_network_image/CHANGELOG.md
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
4.0.3 was tagged and released from main, so the dependency changes move into a new 4.0.4 entry and the package version is bumped to match. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
| Back | FazBrowse Home | New Git URL |
✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Dependency bump, including the example app.
⤵️ What is the current behavior?
The package still requires the lower bounds it shipped with in 4.0.0 (flutter_cache_manager ^3.4.1, material_ui ^1.0.0, octo_image ^2.1.0, mocktail ^1.0.4). The example declares Dart ^3.0.0 / Flutter >=3.10.0 even though it depends on the package, and uses flutter_lints ^4.0.0 and flutter_blurhash ^0.8.2.
🆕 What is the new behavior (if this is a feature change)?
The package requires flutter_cache_manager ^3.4.5, material_ui ^1.3.0, octo_image ^2.1.1 and mocktail ^1.0.5. The example matches the package's SDK constraint and moves to flutter_lints ^6.0.0, flutter_blurhash ^0.9.1 and baseflow_plugin_template ^2.2.1. The example needed no code changes for lints 6, but the new SDK constraint selects the tall style formatter, so example/lib/main.dart is reformatted. Bumps the package to 4.0.4 with its own CHANGELOG entry, since 4.0.3 is already tagged.
💥 Does this PR introduce a breaking change?
No
🐛 Recommendations for testing
Ran locally on Flutter 3.47.4 stable: flutter analyze and flutter test in the package (no issues, 37 tests pass), and flutter analyze in the example (no issues). pub get in the example left the tracked plugin registrants unchanged. The six example builds were not run locally; check them on CI.
📝 Links to relevant issues/docs
material_ui stops at ^1.3.0 because 1.4.0 and later need Dart ^3.13 / Flutter >=3.47. Moving to those is a floor raise, which would be a coordinated breaking release of all three packages. Part of a set of three dependency PRs, one per package.
🤔 Checklist before submitting
🤖 Generated with Claude Code