Skip to content
Back to skills

Promote Beta To Stable

ASecurity

Promote the latest pre-release to a stable release by creating a release branch, bumping the version, and pushing.

  • 21,660 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 3, 2026
ai-agentsgit

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add dyad-sh/dyad --skill promote-beta-to-stable --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Promote Beta To Stable?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Promote Beta To Stable
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dyad-sh-promote-beta-to-stable/badge)](https://www.skillsdirectory.com/skills/dyad-sh-promote-beta-to-stable)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dyad:promote-beta-to-stable
description: Promote the latest pre-release to a stable release by creating a release branch, bumping the version, and pushing.
---

# Promote Beta to Stable

Promote the latest pre-release of dyad-sh/dyad to a stable release.

**IMPORTANT:** This skill MUST complete all steps autonomously. Do NOT ask for user confirmation at any step.

## Instructions

1. **Look up the latest pre-release:**

   ```
   gh release list --repo dyad-sh/dyad --limit 10 --json tagName,isPrerelease
   ```

   Find the most recent release where `isPrerelease` is `true`. Extract the version from the tag name (e.g., `v0.39.0-beta.1`).

   If no pre-release is found, report this and stop.

2. **Get the commit for the pre-release tag:**

   ```
   git fetch upstream --tags
   git rev-parse <tag>
   ```

   Where `<tag>` is the tag name from step 1 (e.g., `v0.39.0-beta.1`).

3. **Determine the release branch name:**

   Parse the version to extract MAJOR and MINOR components. The branch name should be `release-MAJOR.MINOR.x`.

   For example:
   - `v0.39.0-beta.1` → `release-0.39.x`
   - `v1.2.0-beta.3` → `release-1.2.x`

4. **Create the release branch from the pre-release commit:**

   ```
   git checkout -b release-MAJOR.MINOR.x <commit-sha>
   ```

5. **Bump the version in package.json:**

   Read `package.json` and change the `version` field from the pre-release version to the stable version by stripping the pre-release suffix.

   For example:
   - `0.39.0-beta.1` → `0.39.0`
   - `1.2.0-beta.3` → `1.2.0`

   Use the Edit tool to make this change.

6. **Create the commit:**

   Stage and commit the change:

   ```
   git add package.json
   git commit -m "Bump to v<STABLE_VERSION>"
   ```

   For example: `git commit -m "Bump to v0.39.0"`

7. **Push the branch to upstream (dyad-sh/dyad):**

   ```
   git push upstream release-MAJOR.MINOR.x
   ```

8. **Summarize the results:**
   - Report the pre-release that was promoted (e.g., `v0.39.0-beta.1`)
   - Report the stable version (e.g., `v0.39.0`)
   - Report the release branch name (e.g., `release-0.39.x`)
   - Confirm the branch was pushed to upstream

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.