Favicon of updating-package-versions

updating-package-versions Skill

AI Agent SkillDartOpen source

Guides updating dependency versions in published packages to avoid mono-repo resolution failures. Published by flutter in devtools.

What is updating-package-versions Skill?

Guides updating dependency versions in published packages to avoid mono-repo resolution failures. Published by flutter in devtools. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
80/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Developers using devtools

Technical details

Copy skill directory
  • Install or run with Copy skill directory

When to use updating-package-versions Skill

  • Use it for developers using devtools.

Built with

DartCopy skill directory

Editorial notes

Source

  • Creator: flutter
  • Repository: flutter/devtools
  • Skill file: .agents/skills/updating-package-versions/SKILL.md

What it does

Guides updating dependency versions in published packages to avoid mono-repo resolution failures.

Skill instructions

Updating Package Versions When updating dependency versions in published package pubspec.yaml files (devtoolsshared, devtoolsappshared, and devtoolsextensions), follow these rules to protect the local mono-repo workspace graph: - Version Decisions: Decide if it should be a major, minor, or patch version based on your edits: - Breaking changes: Major bump (+1 to first component, others reset to 0). E.g., removals of public constants, properties, getters/setters, or APIs. - New features or deprecation start: Minor bump (+1 to second component, patch resets to 0). - Bug fixes and non-breaking changes: Patch bump (+1 to third component). - Match Exact Versions: Always use the actual version specified in the target package's pubspec.yaml file. - Suffix Preservation: If a requested version contains a suffix like -wip (e.g., 13.0.0-wip), the full string MUST be used in dependency constraints (e.g., devtoolsshared: ^13.0.0-wip). - Prevent Graph Failures: Do not drop the suffix or estimate the

Explore related resources

Frequently asked questions

What is updating-package-versions?

updating-package-versions is a open-source AI agent skill with Copy skill directory. Guides updating dependency versions in published packages to avoid mono-repo resolution failures.

Who is updating-package-versions best for?

updating-package-versions is best for reusing agent instructions, scripts, and references.

How do I install updating-package-versions?

Install or run updating-package-versions using Copy skill directory. Check updating-package-versions for the latest setup command.

Is updating-package-versions actively maintained?

updating-package-versions may need a closer maintenance check before production use.

Share:

Stars
1,723
Forks
399
Last commit
9 days ago
Repository age
8 years
License
BSD-3-Clause

Auto-fetched from GitHub.

Ad
Favicon

 

  
 

Similar to updating-package-versions