dart-resolve-package-conflicts
When pub get fails due to version conflicts, this workflow guides you through surgical lockfile edits to remove only the problematic package entry, then re-resolve to find compatible versions. It covers auditing dependencies with dart pub outdated, upgrading safely with version constraints, and handling retracted packages without wiping your entire lock file.
dart-resolve-package-conflicts fixes pub get failures by surgically removing conflicting packages from your lockfile and re-resolving dependencies.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-28
dart-resolve-package-conflicts fixes pub get failures by surgically removing conflicting packages from your lockfile and re-resolving dependencies. When pub get fails due to version conflicts, this workflow guides you through surgical lockfile edits to remove only the problematic package entry, then re-resolve to find compatible versions. It covers auditing dependencies with dart pub outdated, upgrading safely with version constraints, and handling retracted packages without wiping your entire lock file.
Use it when
- dart-resolve-package-conflicts helps you audit and upgrade Dart dependencies safely using dart pub outdated to identify resolvable versions.
- dart-resolve-package-conflicts teaches surgical editing of pubspec.lock to fix retracted or locked packages.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Similar skills
Install
flutter/agent-plugins/dart-resolve-package-conflicts · repository language: Dart
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to fix dart pub get version conflicts?
dart-resolve-package-conflicts guides you through surgical lockfile edits when pub get fails due to incompatible versions. Rather than deleting your entire pubspec.lock, remove only the problematic package entry from pubspec.lock, then run pub get again to re-resolve dependencies. This targeted approach preserves your other locked versions while finding compatible alternatives for the conflicting package.
What does dart-resolve-package-conflicts cover for dependency auditing?
dart-resolve-package-conflicts helps you audit and upgrade Dart dependencies safely using dart pub outdated to identify resolvable versions. It teaches you how to apply version constraints and caret syntax in pubspec.yaml to control upgrade scope, avoiding version lock while maintaining stability. The workflow prevents accidental major version jumps that break compatibility.
How do I resolve dart package conflicts without wiping my lockfile?
dart-resolve-package-conflicts teaches surgical editing of pubspec.lock to fix retracted or locked packages. Instead of regenerating the entire lock file, identify the conflicting package entry, remove only that section, and run pub get to re-resolve just that dependency against your constraints. This preserves all other pinned versions and speeds recovery from version conflicts.
What version constraint syntax does dart-resolve-package-conflicts explain?
dart-resolve-package-conflicts covers understanding and applying version constraints and caret syntax in pubspec.yaml. The caret operator (^) allows patch and minor updates while pinning the major version, giving you controlled flexibility. The workflow shows how to tighten or loosen these constraints to resolve dependency graph conflicts without manual lockfile regeneration.
How does dart-resolve-package-conflicts handle transitive dependency issues?
dart-resolve-package-conflicts addresses fixing transitive dependency issues by teaching you to identify which direct or transitive package is causing pub get to fail. By surgically removing the problematic entry from pubspec.lock and re-running pub get, the resolver recalculates the entire dependency graph, finding compatible versions that satisfy all constraints downstream.
What workflow does dart-resolve-package-conflicts recommend for major version upgrades?
dart-resolve-package-conflicts provides a major version upgrade workflow that combines auditing with dart pub outdated, adjusting version constraints in pubspec.yaml incrementally, and testing compatibility before committing lockfile changes. This staged approach prevents breaking your entire dependency tree and lets you validate each upgrade step safely.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Managing Dart Dependencies
Contents
- Core Concepts
- Version Constraints
- Workflow: Auditing Dependencies
- Workflow: Upgrading Dependencies
- Workflow: Resolving Version Conflicts
- Examples
Core Concepts
Dart enforces a strict single-version rule for dependencies: a project and all its transitive dependencies must resolve to a single, shared version of any given package. This prevents runtime type mismatches but introduces the risk of "version lock."
To mitigate version lock, Dart relies on version constraints rather than pinned versions in the pubspec.yaml. The pubspec.lock file maintains the exact resolved versions for reproducible builds.
Understand the output columns of dart pub outdated:
* Current: The version currently
(truncated - see the full file via the links below)
File tree — 1 file
skills/dart-resolve-package-conflicts/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Resolve version conflicts when pub get fails due to incompatible package versions”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Flutter Upgrade guides you through SDK version updates with structured phases: research release notes and breaking changes, analyze codebase impact across mise, CI/CD, and Shorebird configurations, generate prioritized task lists, then execute upgrades with validation.
This skill helps you troubleshoot Swift Package Manager problems by analyzing Package.swift and Package.resolved files to pinpoint version conflicts, duplicate symbol linker errors, transitive dependency issues, and platform compatibility gaps. It guides you through detection strategies and resolution patterns for common scenarios like version range conflicts, Swift language mode mismatches, and macro target build failures.
This skill helps construction teams systematically identify and rank Building Information Model conflicts by severity and impact. By automating clash prioritization, it enables teams to allocate resources efficiently and resolve the most critical issues first, reducing project delays and rework costs.
This skill enables automated detection of geometric clashes within Building Information Models, helping construction teams identify conflicts between structural, mechanical, electrical, and plumbing systems before they become costly field issues. By analyzing spatial relationships across BIM datasets, it streamlines coordination workflows and reduces rework during construction phases.
This skill enables AI assistants to automatically establish and configure dependency links between packages within an Nx monorepo workspace. It streamlines the process of wiring up package relationships, helping developers maintain clean dependency graphs and avoid manual configuration errors.
This skill enables automated detection of physical clashes and clearance breaches within BIM models, helping construction teams catch spatial conflicts before they impact the job site. By analyzing element intersections and proximity violations, it supports early problem identification and design coordination workflows.