Skip to content

Prepare Release vnull - #165

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
release-preview
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
release-preview

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

What merging this does:

  1. Stages the new version on npm (not public yet).
  2. Needs a maintainer to approve it on npmjs.com (Staged Packages, 2FA) or with npm stage approve <id>.
  3. Approved within an hour, the running Publish workflow then creates the git tag and GitHub release automatically.
  4. Approved later? Run Publish from the Actions tab (Run workflow). A rejected stage needs a new Prepare Release PR.

Full flow: RELEASE.md

To change the release channel (alpha, beta, rc, stable), run pnpm release:channel <channel> in a separate PR (see RELEASE.md).


Release (2026-11-19)

🏠 Internal

Committers: 1

@kevinhinterlong

Copy link
Copy Markdown
Member

Closing: this one only has an internal docs change, so there's nothing to release (hence the "vnull"). #166 stops Plan Release from opening empty release PRs, and #164 will show up in the next real release's notes. 🙂

@kevinhinterlong
kevinhinterlong deleted the release-preview branch November 19, 2026 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Internal, no release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant