release

Automate Dart package versioning, dependency updates, and publishing to pub.dev.

113|2|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/MelbourneDeveloper/dart_node --skill release-melbournedeveloper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/MelbourneDeveloper/dart_node/tree/main/.claude/skills/release
Command: npx skills add https://github.com/MelbourneDeveloper/dart_node --skill release-melbournedeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex, multi-step process of releasing Dart packages to pub.dev, ensuring consistency and reducing manual errors.

Core Features & Use Cases

  • Version Bumping: Automatically updates package versions across your project.
  • Dependency Management: Switches local dependencies to pub.dev versions for release.
  • Changelog Validation: Verifies that changelogs are updated for new releases.
  • Tiered Publishing: Manages the phased release of interdependent packages.
  • Use Case: Prepare and publish a new major version of your multi-package Dart project to pub.dev with confidence.

Quick Start

Use the release skill to prepare and publish version 1.0.0 of your packages.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate publishing a Dart package to pub.dev?

Automating Dart package publishing to pub.dev is achieved by managing versioning, dependency updates, and changelog validation in a sequential workflow. This ensures packages are correctly prepared and safely published.

How does tiered publishing work for multiple interdependent Dart packages?

Tiered publishing manages the phased release of interdependent Dart packages to pub.dev. It sequentially publishes packages in a safe manner, ensuring local dependencies are correctly switched to pub.dev versions during the process.

Can I automatically bump versions and update local dependencies before a pub.dev release?

Yes, you can automatically bump package versions across your project and switch local dependencies to pub.dev versions. This automation manages the end-to-end release process for Dart packages, reducing manual errors.

Do I need to manually validate my changelog before publishing to pub.dev?

Changelog validation is automatically handled during the Dart package release process. The workflow verifies that changelogs are properly updated for new releases before publishing to pub.dev.

What is the best way to handle a multi-package Dart project release to pub.dev?

The best way to handle a multi-package Dart release is using an automated, tiered publishing workflow. This approach manages versioning, dependency updates, and sequential publishing, ensuring a safe and consistent release.

Why should I use an automated workflow for Dart package releases?

Automating Dart package releases solves the problem of complex, multi-step manual processes. It ensures consistency, reduces manual errors, and manages versioning, dependencies, and tiered publishing across interdependent packages.