releasing-fdb

Automate fdb release workflows with version bumps, verification, and publishing.

44|6|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/andrzejchm/fdb --skill releasing-fdb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: releasing-fdb
Source: https://github.com/andrzejchm/fdb/tree/main/.agents/skills/releasing-fdb
Command: npx skills add https://github.com/andrzejchm/fdb --skill releasing-fdb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end release workflow for the fdb project, handling version bumps, pre-release verification, publishing, and release orchestration to keep releases consistent and low-effort.

Core Features & Use Cases

  • Version bump coordination: updates fdb and fdb_helper lockstep versions across all relevant files.
  • Pre-release checks: runs smoke tests, static analysis, and ensures CI readiness as part of the release.
  • Publishing & release creation: publishes to pub.dev, creates a GitHub release, and updates changelogs and docs.
  • Use case: When preparing a new release, run this skill to automatically bump versions, verify integrity, publish, tag, and create a release entry.

Quick Start

Use the releasing-fdb skill to prepare and publish a new fdb version following the checklist.

Frequently Asked Questions about releasing-fdb

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

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

Automate Dart package releases by bumping versions, running pre-release checks, publishing to pub.dev, and creating GitHub releases. This streamlines the workflow from version bump to publish while ensuring CI readiness and changelog updates.

What is the best way to coordinate lockstep version bumps for multiple packages?

Coordinate lockstep version bumps across multiple packages by simultaneously updating versions in all relevant files. This ensures paired packages like fdb and fdb_helper maintain version parity during patch, minor, or major releases.

How do I prepare a Dart project for a patch, minor, or major release?

Prepare a Dart project for release by running smoke tests, static analysis, and CI readiness checks. Bump versions across multiple files, verify integrity, tag commits, and coordinate release artifacts according to repository conventions.

Does automated releasing handle both pub.dev publishing and GitHub release creation?

Automated releasing handles publishing to pub.dev and creating GitHub releases. It updates changelogs and docs, ensuring consistent release orchestration and low-effort artifact coordination across the project.

Why do I need to run static analysis before publishing a Dart package?

Static analysis is needed before publishing to ensure CI readiness and verify package integrity. Running analysis and smoke tests as part of the release workflow prevents publishing broken or non-compliant code to pub.dev.