Skip to content

Commit

Permalink
[ci:compiler] Only add latest tag to non-experimental
Browse files Browse the repository at this point in the history
It turns out npm sets the latest tag by default so simply removing it didn't change the previous behavior.

The `latest` tag is typically used for stable release versions, and other tags for unstable versions such as prereleases. Since the compiler is still in prerelease, let's set the latest tag only for non-experimental releases to help signal which version is the safest to try out.
  • Loading branch information
poteto committed Oct 18, 2024
1 parent b8ae38f commit 161a096
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions compiler/scripts/release/publish.js
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,21 @@ 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');
}
try {
await spawnHelper(
'npm',
Expand Down

0 comments on commit 161a096

Please sign in to comment.