build: use default channel for prereleases#609
Merged
davidlj95 merged 1 commit intoMay 26, 2024
Conversation
Owner
Author
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @davidlj95 and the rest of your teammates on |
📦 Bundle size (Angular v17)Git ref:
|
📦 Bundle size (Angular v16)Git ref:
|
📦 Bundle size (Angular v18)Git ref:
|
📦 Bundle size (Angular v15)Git ref:
|
davidlj95
force-pushed
the
stacked/build-use-default-channel-for-prereleases-for-now
branch
from
2aaf322 to
85b1214
Compare
davidlj95
changed the title
davidlj95
deleted the
stacked/build-use-default-channel-for-prereleases-for-now
branch
|
🎉 This PR is included in version 1.0.0-beta.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Issue or need
Until now, semantic releases have been done in the
mainchannel by mistake. This meant having amainNPM dist tag for every release. In order to get thelatesttag for pre-releases,tagwas set tolatestinpackage.json'spublishConfig.But that's a misconfiguration workaround. The proper way is to indicate pre-releases on the default channel in semantic release. Which means using the
latestdist tag on npm.Related to this:
npm publishdefault was to addlatesttag to every publish. But as that can be not desired it some scenarios, seems this default may change soonProposed changes
Use default channel for pre-releases in semantic release configuration. Remove
taginpackage.jsonused to addlatestapart frommaindist tag.In order to migrate existing releases to the default channel, manually updated git notes. Git notes are used by semantic release to track in which channel(s) a release has been performed.
Relevant commands:
git for-each-ref 'refs/notes/*' # to list local notes refs--format '%(refname)' --shellgit ls-remote 'refs/notes/*' # to list remote notesgit fetch origin 'refs/notes/*:refs/notes/*' # to fetch remote notesgit update-ref -d 'refs/notes/<ref>' # to remove local refgit push --delete origin 'refs/notes/<ref>' # to remove remote refgit notes --ref <note-ref> add -f -m 'content' <ref> # to add a note to a refNotes content is (to indicate default branch):
{"channels":[null]}Notes ref name is (recently changed though)
https://github.com/semantic-release/semantic-release/blob/v23.1.1/lib/git.js#L344-L350
Name was before
semantic-releasefor all tagsQuick reminders