chore: release (rc)#2253
Merged
Merged
Conversation
✅ Deploy Preview for solid-start-landing-page ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
July 26, 2026 18:05
cb785ec to
fd23d57
Compare
commit: |
birkskyum
approved these changes
Jul 26, 2026
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 26, 2026 20:43
fd23d57 to
0856c34
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@solidjs/start@2.0.0-rc.5
Minor Changes
4c803e5: Add
serialization.pluginsto configure custom Seroval plugins for server functions.Values Seroval has no built-in support for (Mongo's
ObjectId, Prisma'sDecimal,Temporal, and other custom classes) previously threw when returned from or passed to a server function. Point the new option at a module whose default export is an array of plugins:The module is bundled into both the client and the server so both ends of a server function agree on the format, so it must not import server-only code. SolidStart's built-in plugins keep precedence. Only server-function and action payloads are affected; the SSR hydration payload is serialized by
solid-js/web.Also adds a
@solidjs/start/serializationentrypoint re-exporting Seroval'screatePlugin,OpaqueReference, and plugin types, so plugin authors stay on the same Seroval version SolidStart serializes with.Patch Changes
e117d91: Route module ids now end in the source extension, so ecosystem plugins apply inside
src/routes.Route files are imported through an id carrying the picked exports in the query (
routes/api.ts?pick=GET), which left the id ending in the export name. Plugins whose filter is anchored on the file extension (/\.[cm]?[jt]sx?$/, the default forunplugin-auto-import,unplugin-macrosand others) silently skipped every route file. The id now ends with alang.<ext>marker, the same convention Vue SFCs use for?vue&type=script&lang.ts. Chunk filenames are unchanged.d8f1ea8: Apply the configured
nonceto the two script tags that were still missing it, so a strictscript-srcCSP no longer needsunsafe-inline:<script>window.location=...</script>) now carries the nonce.27fca88: Fix actions returning
json()orreload()leaving no-JS form submissions stranded on the/_serverendpoint. These responses carry a value rather than a destination, so the redirect issued for progressive-enhancement submissions had noLocationheader. It now falls back to the submitting page, and the response value is unwrapped into the flash cookie souseSubmission().resultmatches the JS path.75debc3: Scope the built-in
~alias to the app package, so files in other workspace packages can map~to their own root through an importer-aware plugin such asvite-tsconfig-paths. In stylesheets and asset URLs (CSS@import,url(),new URL(..., import.meta.url))~still always means the app root, since Vite resolves those without running plugins.