release-devbox

Automates Devbox CLI releases including version recommendation, release notes, and draft or publish flow.

12.3k|358|Updated Aug 18, 2022
One-click install
npx skills add https://github.com/jetify-com/devbox --skill release-devbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-devbox
Source: https://github.com/jetify-com/devbox/tree/main/.agents/skills/release-devbox
Command: npx skills add https://github.com/jetify-com/devbox --skill release-devbox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cutting a Devbox CLI release involves many ordered, failure-prone steps — version bumping, changelog writing, draft creation, goreleaser builds, flake.nix bumps, and publish timing — and doing them in the wrong order has repeatedly broken past releases. This Skill encodes the correct pipeline and the judgment calls so releases ship cleanly.

Core Features & Use Cases

  • Version Recommendation: Analyzes commits since the last release via devbox run release-changes and recommends a semver bump following the project's pre-1.0 conventions (breaking changes take a minor bump, everything else a patch).
  • Release Notes Authoring: Rewrites GitHub's generated changelog into user-facing notes in the established house style, with breaking changes first, grouped fixes, and per-PR attribution.
  • Draft and Publish Pipeline: Drives scripts/release.ts through draft-first or direct-publish flows, handles flake.nix bump PRs, and resumes idempotently after failures.
  • Stuck-Release Diagnosis: Uses devbox run release-status plus a symptom table to fix failed cli-release runs, empty drafts, and Docker image build failures.
  • Use Case: A maintainer asks to ship version 0.18.0; the Skill inspects pending commits, drafts notes, gets sign-off, runs the release script in the background, and verifies the published assets.

Quick Start

Ask the agent to cut a new Devbox release and it will review pending changes, recommend a version, draft the release notes for your approval, and run the draft or publish pipeline.

Frequently Asked Questions about release-devbox

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

FAQPage Schema
How do I cut a new Devbox CLI release?

Run devbox run release-changes to see pending commits and the recommended version, write release notes in the house style, then run scripts/release.ts with --draft or --publish. The draft-first flow is the safe default since it lets you review before going live.

How should Devbox release notes be written?

Fetch the generated changelog with gh api repos/jetify-com/devbox/releases/generate-notes, then rewrite it into user-facing sections: breaking changes first with migration guidance, then features, fixes, and maintenance. Every bullet keeps its author attribution and PR link.

What version bump does a breaking change get in Devbox?

Devbox is pre-1.0, so breaking changes take a minor bump (0.17.5 to 0.18.0) and everything else, including new features, takes a patch bump. The release-changes command prints the recommendation, but sanity-check it against the actual diff.

Why did the Devbox Docker image release fail after publishing?

The docker-image-release workflow fires on the release event and immediately downloads release tarballs, so publishing before goreleaser uploads assets fails the build. Re-run docker-image-release via workflow_dispatch with the tag once assets exist.

Can a failed Devbox release be resumed?

Yes, every step in scripts/release.ts is idempotent, so fix the underlying cause and re-run the same command to pick up where it stopped. Use devbox run release-status to see the tag, draft, asset count, and cli-release result in one shot.