// Guides updating dependency versions in published packages to avoid mono-repo resolution failures.
Find and close obsolete, stale, or not reproducible issues in the flutter/devtools repository.
Use when documenting changes in CHANGELOG.md files for devtools_shared, devtools_app_shared, or devtools_extensions.
Adds copyright headers to files based on file type. Use when creating new files or when asked to verify copyright headers.
Adds user-facing change descriptions to DevTools release notes. Use when documenting improvements, fixes, or new features in the NEXT_RELEASE_NOTES.md file.
Guides the creation of high-quality, effective skills for agentic workflows. Use when creating or modifying skills in the .agents/skills/ directory.
Prepare a pull request by running presubmit with fixes. Use when preparing to commit or send a PR.
| name | updating-package-versions |
| description | Guides updating dependency versions in published packages to avoid mono-repo resolution failures. |
When updating dependency versions in published package pubspec.yaml files (devtools_shared, devtools_app_shared, and devtools_extensions), follow these rules to protect the local mono-repo workspace graph:
pubspec.yaml file.-wip (e.g., 13.0.0-wip), the full string MUST be used in dependency constraints (e.g., devtools_shared: ^13.0.0-wip).devtools_shared, devtools_app_shared, and devtools_extensions) MUST NOT depend on unpublished packages like devtools_app or devtools_test.flutter pub get in the repository to ensure version solving is satisfied. If this returns errors, you should fix the errors and try again.packages/devtools_app/pubspec.yaml:
dt update-version tool to update the devtools_app version.