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:
Michael Wang
2026-11-17 04:35:57 +00:00
committed by GitHub
parent 0ad24ba83f
commit 9fae4ffd81
3 changed files with 16 additions and 1 deletions
+5
View File
@@ -296,6 +296,11 @@ test("the publish job checks the release channel without repo scripts", () => {
assert.equal(check("push", "0.9.55-alpha.1;id", "true"), 1);
assert.equal(check("push", "0.9.55-latest.1", "true", "latest"), 1);
assert.equal(check("push", "0.9.55-hdr.1", "true", "hdr"), 0);
assert.equal(check("push", "0.9.55-beta.1", "true", "beta"), 0);
assert.equal(check("push", "0.9.55-LATEST.1", "true", "LATEST"), 1);
assert.equal(check("push", "0.9.55-Latest.1", "true", "Latest"), 1);
assert.equal(check("push", "0.9.55-Alpha.1", "true", "Alpha"), 1);
assert.equal(check("push", "0.9.55-stable.1", "true", "stable"), 1);
});
test("the publish job takes only tarballs that npm reads the way the check does", () => {