skills.rest
dyad-sh
dyad-shOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dyad:promote-beta-to-stable

Promotes the latest pre-release to a stable release branch with version bump and push.

21.4k|2.6k|Updated Apr 11, 2025
Search Tags:#release management#Git#pre-release#version bump#SemVer#gitHub cli#release branch
One-click install
npx skills add https://github.com/dyad-sh/dyad --skill dyad-promote-beta-to-stable
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dyad:promote-beta-to-stable
Source: https://github.com/dyad-sh/dyad/tree/main/.claude/skills/promote-beta-to-stable
Command: npx skills add https://github.com/dyad-sh/dyad --skill dyad-promote-beta-to-stable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually promoting a beta pre-release to a stable release involves error-prone steps: finding the right tag, creating a correctly named release branch, editing package.json, and pushing to upstream. This Skill automates that entire release promotion workflow for the dyad-sh/dyad repository.

Core Features & Use Cases

  • Pre-release Discovery: Uses the GitHub CLI to list releases and identify the most recent pre-release tag (e.g., v0.39.0-beta.1).
  • Release Branch Creation: Derives the MAJOR.MINOR version and creates a release branch (e.g., release-0.39.x) from the exact pre-release commit.
  • Automated Version Bump: Strips the pre-release suffix from package.json, commits the change, and pushes the branch to upstream.
  • Use Case: A maintainer wants to ship v0.39.0 after beta testing. The Skill finds v0.39.0-beta.1, creates release-0.39.x, bumps the version to 0.39.0, and pushes the branch without any manual git commands.

Quick Start

Promote the latest dyad beta pre-release to a stable release branch and push it to upstream.

Frequently Asked Questions about dyad:promote-beta-to-stable

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

FAQPage Schema
How do I promote a beta pre-release to a stable release on GitHub?▼

Use the GitHub CLI to find the latest pre-release tag, create a release branch from that commit, strip the pre-release suffix from the version in package.json, commit the change, and push the branch to upstream. This Skill automates all of these steps.

How to create a release branch from a git tag?▼

Fetch tags from upstream, resolve the tag to its commit SHA with git rev-parse, then run git checkout -b release-MAJOR.MINOR.x <commit-sha>. The branch name is derived from the major and minor version components of the tag.

Does this release promotion require the GitHub CLI?▼

Yes, the gh CLI is required to list releases and identify the latest pre-release via gh release list --repo dyad-sh/dyad. Git with an upstream remote pointing to dyad-sh/dyad is also required for fetching tags and pushing the branch.

What happens if no pre-release is found?▼

The Skill reports that no pre-release exists and stops without making any changes. It does not create branches, modify package.json, or push anything when there is no beta tag to promote.

How is the stable version number determined from a beta tag?▼

The pre-release suffix is stripped from the version string. For example, v0.39.0-beta.1 becomes 0.39.0, and the release branch is named release-0.39.x based on the major and minor components.

Related Skills

Explore More Software Engineering Skills→
nexus-a1nexus-a1

release

Tag new versions and generate AI-authored release notes from commit history.

Community
Advanced
enclawedenclawed
2

enclawed-release-maintainer

Orchestrate Enclawed releases with version alignment, validation, and npm/macOS publishing.

Community
Advanced
ComposioHQComposioHQ
30.0k

cli-release

Build, promote, and verify Composio CLI binary releases through GitHub Actions workflows.

Official
Advanced
RoxabiRoxabi
9

promote

Automate staging-to-main branch promotion with pre-flight checks, versioning, and pull request creation.

Official
Advanced