Repository navigation
chore: prepare the 2.0.0 stable release - #731
Merged
Merged
Conversation
Exit changesets pre mode so the next version is 2.0.0 and changeset publish tags it latest, move the solid-js/@solidjs/web peers to ^2.0.0, and drop README wording that points at next prereleases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWKegJTJmg5nmox4u4v
🦋 Changeset detectedLatest commit: a6313f7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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
Release prep for
@solidjs/router2.0.0, to go with solid-js 2.0.0 on npmlatest..changeset/pre.jsonmodeexit). I ranchangeset versionon a copy and it produces 2.0.0, with every pending changeset in one 2.0.0 CHANGELOG section.changeset publishthen tags itlatest.release.ymlhas no hard-coded dist-tag. The tag comes only from pre mode, so no change is needed. Pushes tonextstill trigger it, andworkflow_dispatchis still the manual fallback.solid-jsand@solidjs/webare now^2.0.0(were^2.0.0-rc.19), with a patch changeset.filesystem-routingstays>=0.4.0.nextprereleases" to talk about earlier versions and<A>instead.src/change, so client bundle 0 B.Merge order: #729 (devDeps on 2.0.0, test expectations) and #730 (#724 fix) first, then this. The changesets "Version Packages" PR that follows is the release itself.
After publishing,
@solidjs/router@latestmoves off1.0.3(the Solid 1 line). I suggest pinning that line first:npm dist-tag add @solidjs/router@1.0.3 v1-latest, matching solid-jsv1-latest.Generated by Claude Code