Repository navigation
ci: release and test the 1.x branch to the v1-latest dist-tag - #741
Merged
Merged
Conversation
…-tag main is now the 2.0 line, so the 1.x branch's workflows (which only triggered on main) never ran, and changeset publish would have moved npm latest off 2.0. Release, test and dist-typecheck now run on 1.x, changesets uses 1.x as its base branch, and publishes go to v1-latest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWLp9qyH355tWfPxwbi
|
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
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.
Requested by Ryan · project thread
Now that
mainis the 2.0 line, the1.xbranch's CI still pointed atmain, so:1.x, so a 1.x changeset would never get a Version Packages PR or publish.changeset publishwould have published 1.x to npmlatest, which is currently2.0.0(v1-latestis1.0.3).1.x(Parallel Routes #426, feat:batchedQuery#607).Changes, all on
1.xonly:release.yml,test.yml,dist-typecheck.yml: trigger on1.xinstead ofmain..changeset/config.json:baseBranchis1.x.package.json:releaserunschangeset publish --tag v1-latest, andpublishConfig.tagisv1-latestfor a manualnpm publish.Router is a single package, so the
--tagflag is enough here (no need for solid'spublish-solid-js.mjsworkaround). npm trusted publishing names the workflow file, which is stillrelease.yml.Generated by Claude Code