Update Examples Dependencies
Developmentupdate-examples-dependenciesUpdate Examples Dependencies is an Agent Skill for development published in the rodydavis/signals.dart repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Update all the `./examples` dependencies to the latest repository/third-party versions and fix any compiler or analysis issues.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/rodydavis/signals.dart/blob/HEAD/.agents/skills/update-examples-dependencies/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/update-examples-dependencies, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Update Examples Dependencies & Code Fixes
This skill provides a systematic and automated workflow to update dependencies in all Dart/Flutter examples located in the ./examples directory and fix any code compilation, deprecation, or linter warnings that arise.
Objective
Ensure all ./examples packages are upgraded to target the latest core package versions (e.g. signals) of the repository, run a full pub upgrade on third-party dependencies to prevent stale locks, and repair any broken code or deprecation warnings under analysis.
Workflow
1. Run the Automated Update Script
Locate the helper script at scripts/update_dependencies.dart or within this skill's scripts directory:
dart run .agents/skills/update-examples-dependencies/scripts/update_dependencies.dart
This script will:
- Read
packages/signals/pubspec.yamlto detect the current package version ofsignals. - Recursively find all
pubspec.yamlfiles inside./examples/. - Replace the
signalsdependency version constraint with the exact latest version constraint (e.g.,^6.3.1). - Execute
flutter pub upgradeordart pub upgradeon each example package.
2. Bootstrap the Workspace
After upgrading individual package pubspecs, link the workspace packages and ensure they resolve successfully by running:
melos bootstrap
3. Analyze and Fix Code Issues
With all packages upgraded, run static analysis to check for breaking changes or new warnings:
melos run analyze
For any deprecations (such as v6 to v7 API transitions or external package changes):
- Inspect the file and reference standard migration rules (e.g.,
migration-6-to-7if migrating to v7). - Refactor the code in place to use modern, non-deprecated APIs.
- Fix all compiler errors and static analysis warnings until
melos run analyzesucceeds cleanly.