Skip to content

fix: publish promoted prereleases as stable #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Nsttt merged 1 commit into from
Oct 6, 2026
Merged

fix: publish promoted prereleases as stable #31

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,9 @@ name: Release

on:
release:
types: [published]
# `published` covers pre-releases, including ones published from drafts.
# `released` covers stable releases and pre-releases switched to stable.
types: [published, released]
workflow_dispatch:
inputs:
version:
Expand All @@ -28,6 +30,11 @@ concurrency:

jobs:
publish:
# A stable release fires both `published` and `released`; publish once.
if: >-
github.event_name != 'release' ||
github.event.action == 'released' ||
github.event.release.prerelease
runs-on: ubuntu-latest
environment: Publish
steps:
Expand Down
2 changes: 1 addition & 1 deletion docs/RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ The workflow creates a Changesets snapshot version and publishes it under the np

A GitHub prerelease also publishes under `next`. Its tag must match the base version in `packages/nuxt/package.json`; the workflow derives a rerun-safe `<base>-next.<workflow-run-id>` npm version.

Converting that GitHub prerelease to a stable release does not republish it. After the stable version PR is merged, run `Release` manually with `version=latest` and `branch=main`.
To promote that prerelease, edit the GitHub release and switch it from pre-release to the latest release. That runs `Release` again and publishes the base version with the npm `latest` dist-tag.

## First `0.1.0` checklist

Expand Down
Loading