ci: publish pre-releases to the latest dist-tag - #21
Merged
Conversation
While pre-1.0, the newest release is what consumers should get by default, so every tag now publishes to `latest` instead of routing -beta/-alpha/-rc to a separate channel. Stops `latest` from going stale on an old version. Pre-release detection is kept (it drives the GitHub Release --prerelease flag). README install line reverted to a plain `npm install` to match.
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.
Why
npm install @ilq/grapesjs-angularwas resolving to2.0.0-beta.1(2 months old, pre-React-parity API) becausepublish.ymlrouted-betatags to thebetadist-tag and never advancedlatest. While the library is pre-1.0, the newest release should be the default install.Change
publish.yml— every tag now publishes with--tag latest(npm's default) instead of routing-alpha/-beta/-rcto separate channels. A comment notes to revisit once a stable release needs its own pre-release channel. Pre-release detection is preserved — it still drives the GitHub Release--prereleaseflag.README.md— install line reverted to plainnpm install @ilq/grapesjs-angular grapesjs(the npm-package link added earlier stays).Note
This only governs future tags. The current
latest→beta.1is fixed out-of-band with a one-timenpm dist-tag add @ilq/grapesjs-angular@2.0.0-beta.2 latest(the publish job uses OIDC Trusted Publishing, so there's no token to do it from CI today).