Repository navigation
docs: drop release-candidate wording from the 2.0 docs - #1700
Merged
Merged
Conversation
The overview note, the site description, the router migration requirement, the server components caution and the filesystem-routing codeSplitting note no longer describe Solid 2.0 as a release candidate or name RC builds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWNxvzLd4SQ3p3kgdA1
|
|
✅ Deploy Preview for solid-docs-v2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
Description(required)
Removes the places where the 2.0 docs describe themselves as a release candidate. This PR can merge before the stable tag.
(0)index.mdx): the "These docs cover the release candidate" note, which said APIs may change before stable, is now a one-line "These docs cover Solid 2.0" note that links the 1.x docs.vite.config.ts): this is the meta description and llms header text. It now reads "Documentation for Solid 2.0, …".solid-jsand@solidjs/web2.0".codeSplitting: the note that eager delivery needs a router newer than2.0.0-next.14is removed, because every 2.0 router release meets that.Left as is on purpose:
pnpm add @solidjs/router@nextin router setup. Until router 2.0.0 is published aslatest,@solidjs/routerwithout a tag installs 1.x. Change it after the router release.vite.config.tsandsource_reffrontmatter.Before starting, I checked open PRs, remote branches and recent v2-rebuild commits. None of them removes this wording.
Checks:
check:types,prettier --check,lint:tone(0 errors) andpnpm buildpass, and the built site no longer contains "release candidate".Related issues & labels
Generated by Claude Code