is there a way to do nightly / unstable releases?

Affected Packages

Idk

Problem

I may not be ready for a release, but i may want folks to be able to test out changes without manually doing pre-reloason

Proposed solution

Provide an unstable option in config. When true, every merge is published (provided the changesets declare changes) with the git sha appended to the version. This uses the 'unstable' tag on npm, and does not create github releasen, nor remove the changeset files

You can use the following:

yarn changeset version --snapshot unstable
yarn build
yarn changeset publish --tag unstable

However, problem I had with that, is if no changes are found version throws an error

yeah, for unstable releases, I wouldn't care about noting changelog entries -- I (and I'm sure a good number of folks) review their changelog / changesets before actual release, proofread, etc etc -- all unneeded for unstable

I would also really like this feature. When the changeset publish PR opens (and each time it updates) or on merge to main - an unstable version should be published.

Currently to do integration testing when multiple changesets come together we have to manually publish versions or use workarounds like links and yalc.

For now we've implemented this ourselves with a github action

name: Unstable/nightly release

on:
  push:
    branches: [main]

jobs:
  unstable-release:
    name: Unstable/nightly release
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/checkout@v3
      - uses: pnpm/[email protected]

      - name: Use Node.js 16.14.0
        uses: actions/setup-node@v3
        with:
          node-version: 16.14.0
          cache: "pnpm"
          node-version-file: ".nvmrc"
          registry-url: "https://registry.npmjs.org/"

      - name: Install dependencies
        run: pnpm install
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

      - name: Generate unstable changeset
        run: pnpm changeset version --snapshot next
        
      - name: Build packages
        run: pnpm build
        
      - name: Publish unstable packages
        run: pnpm changeset publish --tag next

@jake-slashid

@jake-slashid
Is this working the way you expect?

I guess your package versions are of the format 0.0.0-next-YYYYMMDDHHMMSS?

Document nightly usecase and pkg.pr.new

This is documented on the site at 8f84326 now

Add new docs site (changesets#1979)

Navigation Menu

Repository navigation

is there a way to do nightly / unstable releases? #1091

Affected Packages

Problem

Proposed solution

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

is there a way to do nightly / unstable releases? #1091

Description

Affected Packages

Problem

Proposed solution

Activity

nsams commented on Mar 20, 2023

NullVoxPopuli commented on Mar 20, 2023

jake-slashid commented on Aug 25, 2023

jake-slashid commented on Aug 25, 2023

archiewood commented on Nov 13, 2024

bluwy commented on Jun 30, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions