Skip to content

[ci:compiler] Only add latest tag to non-experimental#31288

Merged
poteto merged 1 commit into
mainfrom
pr31288
Oct 18, 2024
Merged

[ci:compiler] Only add latest tag to non-experimental#31288
poteto merged 1 commit into
mainfrom
pr31288

Conversation

@poteto
Copy link
Copy Markdown
Contributor

@poteto poteto commented Oct 18, 2024

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.

Stack created with Sapling. Best reviewed with ReviewStack.

@vercel
Copy link
Copy Markdown

vercel Bot commented Oct 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
react-compiler-playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 18, 2024 5:21pm

@facebook-github-bot facebook-github-bot added CLA Signed React Core Team Opened by a member of the React Core Team labels Oct 18, 2024
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed React Core Team Opened by a member of the React Core Team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants