You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removed chore/* branches from prerelease channels since they're for
internal changes not meant for client distribution. Only fix/* and
feat/* branches (plus explicit beta) will publish now.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: PRERELEASE_SETUP.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,14 @@
2
2
3
3
## Overview
4
4
5
-
This repository uses branch-specific prerelease channels for publishing packages from feature branches, fix branches, etc. Each branch category gets its own npm dist-tag:
5
+
This repository uses branch-specific prerelease channels for publishing packages from feature branches and fix branches. Each branch category gets its own npm dist-tag:
6
6
7
7
-`fix/*` → `2.22.1-fix.1` (dist-tag: `fix`)
8
8
-`feat/*` → `2.22.1-feat.1` (dist-tag: `feat`)
9
-
-`chore/*` → `2.22.1-chore.1` (dist-tag: `chore`)
10
9
-`beta` → `2.22.1-beta.1` (dist-tag: `beta`)
11
10
11
+
Note: `chore/*` branches do not publish - they're for internal changes not meant for client distribution.
12
+
12
13
## GitHub Environment Setup
13
14
14
15
### 1. Create the Publish-Prerelease Environment
@@ -28,7 +29,7 @@ Since semantic-release now controls which branches can publish based on `release
0 commit comments