Resolve Dart package version conflicts
Fix pub get failures: audit, upgrade and surgically resolve Dart dependency conflicts
- What
- Fix pub get failures: audit, upgrade and surgically resolve Dart dependency conflicts
- Cost
- Free
- Needs
- Dart SDK installed; a Dart/Flutter project with pubspec.yaml
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official Dart team's dependency playbook: how Dart's single-version rule and version constraints work, how to read `dart pub outdated` columns (current / upgradable / resolvable / latest), when to use caret syntax and `dart pub upgrade --tighten`, enforcing lockfiles in CI with `--enforce-lockfile`, and — the centerpiece — resolving conflicts by surgically deleting only the conflicting package's block from `pubspec.lock`, never by nuking the whole lockfile. By @dart-lang, listed here with credit to its creator. Honest caveats: official Dart-team skill — conventions-first guidance; frontmatter notes AI-assisted authorship, treat as conventions to verify; lockfile surgery requires `git`-committed pubspec.lock to be safely reversible. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
It explains the single-version rule and version constraints, how to read dart pub outdated columns, when to use caret syntax and dart pub upgrade --tighten, how to enforce lockfiles in CI, and how to resolve conflicts by deleting only the conflicting block from pubspec.lock.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 0d9f1c4Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Dart SDK installed; a Dart/Flutter project with pubspec.yaml Install "Resolve Dart package version conflicts" for me. Give my agent the dependency workflow — understanding version constraints, auditing with dart pub outdated, upgrading with --tighten, enforcing lockfiles in CI, and surgically resolving version conflicts in pubspec.lock Repository: https://raw.githubusercontent.com/dart-lang/skills/0d9f1c4a0ae29d6f5180bf6143d7997ec3bacf49/skills/dart-resolve-package-conflicts/SKILL.md Pinned version: install the code at commit 0d9f1c4a0ae29d6f5180bf6143d7997ec3bacf49 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the dart-lang-skills-dart-resolve-package-conflicts skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "dart-lang-skills-dart-resolve-package-conflicts". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. commit pubspec.lock to git before any lockfile surgery). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 0d9f1c4 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.