update-examples-dependencies

To update Dart and Flutter example dependencies, the skill recursively scans pubspec.yaml files under ./examples, runs flutter pub upgrade or dart pub upgrade, and refreshes dependency constraints to keep example packages compatible with core packages.

Fixing analyzer failures after a pub upgrade requires bootstrapping the workspace with melos bootstrap, running melos run analyze, and iterating code fixes for breaking API changes, deprecations, and new linter warnings until the analysis passes.

Yes, melos works with Flutter example packages by bootstrapping the monorepo workspace to ensure workspace consistency, then verifying correctness across all example packages by running melos run analyze after upgrading dependencies.

The best way to keep signals package dependencies compatible is to update dependency constraints to the latest compatible version and run pub upgrade commands per example, preventing stale lockfiles and ensuring workspace consistency.

Flutter example projects break when upgrading third-party dependencies due to breaking API changes, deprecations, and new analyzer warnings that require refactoring code to maintain compatibility with rapidly changing core packages.

Recursively scanning pubspec.yaml files for dependency updates is limited to Dart and Flutter example packages under ./examples, requiring melos bootstrap and successful melos run analyze completion to ensure workspace consistency.