mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-19 11:26:02 +00:00
ci(publish): a prerelease tag publishes only to an allow-listed dist-tag (#7963)
The publish job took the npm dist-tag from the pushed tag's suffix and refused only an exact "latest". A tag such as v1.2.3-LATEST.1, or one with a new suffix, still named its own dist-tag. The job's channel check now accepts only alpha, beta, rc, next, canary, hdr, native and desktop, matched exactly.
This commit is contained in:
@@ -6,7 +6,7 @@ description: How HyperFrames keeps alpha-only work out of stable releases.
|
||||
HyperFrames publishes two release channels:
|
||||
|
||||
- Stable releases use versions like `0.4.24` and publish to the npm `latest` dist-tag.
|
||||
- Prereleases use versions like `0.4.24-alpha.1` and publish to the npm dist-tag named by the prerelease suffix, such as `alpha`.
|
||||
- Prereleases use versions like `0.4.24-alpha.1` and publish to the npm dist-tag named by the prerelease suffix, such as `alpha`. The suffix must be one of `alpha`, `beta`, `rc`, `next`, `canary`, `hdr`, `native` or `desktop`, in lower case. The publish workflow refuses any other suffix before it publishes.
|
||||
|
||||
## Branch policy
|
||||
|
||||
|
||||
Reference in New Issue
Block a user