Skip to content

Commit

Permalink
add "next" branch for prereleases
Browse files Browse the repository at this point in the history
It is strongly recommended to do prerelease before releasing a stable
release because we cannot cancel publishing a package n npm.js; once
a package is uploaded, its version number is occupied forever even if
it is unpublished.  Making a stable version number unavailable due to
failure of uploading or packaging is quite unsatisfactory.  Prerelease
allows us to make sure that a package can be successfully created and
uploaded before stable release.
  • Loading branch information
uenoB committed Dec 10, 2023
1 parent 1cb910f commit a922da4
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/ci.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ jobs:
- run: pnpm --recursive --sequential run build
release:
needs: check
if: github.ref == 'refs/heads/latest'
if: github.ref == 'refs/heads/latest' || github.ref == 'refs/heads/next'
permissions:
contents: write
issues: write
Expand Down
5 changes: 4 additions & 1 deletion release.js
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,10 @@ for (const name of packages) {
nextRelease.notes %>`

const options = {
branches: ['latest'],
branches: [
{ name: 'latest' },
{ name: 'next', channel: 'next', prerelease: true }
],
tagFormat: name + '-v<%= version %>',
plugins: [
wrap(commitAnalyzer),
Expand Down

0 comments on commit a922da4

Please sign in to comment.