chore: exit changeset pre-mode - #2279
Open
birkskyum wants to merge 1 commit into
Open
Conversation
|
| Name | Type |
|---|---|
| @solidjs/start | Patch |
| landing-page | Patch |
| tests | Patch |
| fixture-bare-js | Patch |
| fixture-bare | Patch |
| fixture-basic | Patch |
| fixture-css | Patch |
| fixture-experiments | Patch |
| fixture-hackernews | Patch |
| fixture-notes | Patch |
| fixture-todomvc | Patch |
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
✅ Deploy Preview for solid-start-landing-page ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
commit: |
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.
Now that we are feature complete and have resolved all the bugs we planned for initial Start 2 release (the remainig issues are either Feature Requests, or bugs in other libraries), this is how we opt out of the changeset pre.json, so that we get a changeset release PR we can prepare for launch.
We have docs / annoucement etc. ready to go.
There's a bit of changeset tinkering, because of the way we stepped from alpha to beta to rc, but I can handle that in the changeset PR when this pre-tag is gone.