[cd] Use SemVer prerelease type for NPM dist-tag#94622
Draft
eps1lon wants to merge 2 commits into
Draft
Conversation
...or, if it's not a prerelase, use `latest` if it's the highest version or `backport` otherwise
Contributor
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URLCommit: f740d40 |
Contributor
Failing test suitesCommit: f740d40 | About building and testing Next.js
Expand output● create-next-app with package manager yarn › should use yarn for --use-yarn flag with example ● create-next-app with package manager yarn › should use yarn when user-agent is yarn with example
Expand output● app dir - metadata static routes cache › should generate different content after replace the static metadata file
Expand output● create-next-app with package manager yarn › should use yarn for --use-yarn flag with example ● create-next-app with package manager yarn › should use yarn when user-agent is yarn with example |
…ints at a prerelease
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
...or, if it's not a prerelase, use
latestif it's the highest version orbackportotherwiseRemoves one more place where the tags are hardcoded. We always mirrored SemVer prerelease types and NPM dist tags (except how stable releases are handled). We can just use the SemVer prerelease as the source of truth to avoid future mistakes.
Now we also undraft any prerelease not just canary (felt like an oversight from previous changes).
Also includes [cd] Allow tagging semver-lower releases as
@latestif@latestpoints at a prereleasetest plan
with different versions in
lerna.json