From cf2c79b5ff01a3fbe318910c242ff159cd963fdd Mon Sep 17 00:00:00 2001 From: Lauren Tan Date: Tue, 7 Oct 2025 11:10:04 -0700 Subject: [PATCH] [compiler] Update release script for latest tag Updates our release script so we can publish to the `latest` tag. --- compiler/scripts/release/publish.js | 20 ++++---------------- 1 file changed, 4 insertions(+), 16 deletions(-) diff --git a/compiler/scripts/release/publish.js b/compiler/scripts/release/publish.js index 99c47384251c..f9c42d15636b 100755 --- a/compiler/scripts/release/publish.js +++ b/compiler/scripts/release/publish.js @@ -68,7 +68,7 @@ async function main() { .option('tag', { description: 'Tag to publish to npm', type: 'choices', - choices: ['experimental', 'beta', 'rc'], + choices: ['experimental', 'beta', 'rc', 'latest'], default: 'experimental', }) .option('tag-version', { @@ -181,21 +181,9 @@ async function main() { if (otp != null) { opts.push(`--otp=${otp}`); } - /** - * Typically, the `latest` tag is reserved for stable package versions. Since the the compiler - * is still pre-release, until we have a stable release let's only add the - * `latest` tag to non-experimental releases. - * - * `latest` is added by default, so we only override it for experimental releases so that - * those don't get the `latest` tag. - * - * TODO: Update this when we have a stable release. - */ - if (argv.tag === 'experimental') { - opts.push('--tag=experimental'); - } else { - opts.push('--tag=latest'); - } + + opts.push(`--tag=${argv.tag}`); + try { await spawnHelper( 'npm',