ci: Version Packages (rc) - #8468
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the 鈿欙笍 Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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 solid-router-v2-pre, this PR will be updated.
solid-router-v2-preis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonsolid-router-v2-pre.Releases
@tanstack/solid-router@2.0.0-rc.9
Patch Changes
#8467
0dc3a9e- Bump solid-js and @solidjs/web to ^2.0.0-rc.9 and @solidjs/vite-plugin to ^3.0.0-next.44 across the monorepo (with @solidjs/babel-plugin 2.0.0-rc.9 for the webpack path). @solidjs/vite-plugin 3.0.0-next.44 peer-requires solid-js ^2.0.0-rc.9 and ships the rc.9 compiler.rc.9 changed
serverFunctionUrlto describe aGET()reference's own call (serverFunctionUrl(fn, ...args)) and moved the id-based form-post address toserverFunctionActionUrl/parseServerFunctionActionUrl(serverFunctionUrlreturns/_server/<id>, but the server function invocation actually fetches/_server/data/<id>, making serverFunctionUrl return value unusable for preloading聽solidjs/solid#3440); @tanstack/solid-start's server-function handler now uses those.Rsbuild apps:
@rsbuild/plugin-solid@2.0.0-rc.0hard-pins the rc.6 compiler, which emits the old delegated-event key (el.$$click) that the rc.9 runtime no longer reads (_$$click), so delegated handlers never fire. Until the plugin ships an rc.9-based release, override its@solidjs/compilerand@solidjs/babel-pluginto 2.0.0-rc.9 (the monorepo does this inpnpm-workspace.yaml).@tanstack/solid-router-devtools@2.0.0-rc.7
Patch Changes
#8467
0dc3a9e- Bump solid-js and @solidjs/web to ^2.0.0-rc.9 and @solidjs/vite-plugin to ^3.0.0-next.44 across the monorepo (with @solidjs/babel-plugin 2.0.0-rc.9 for the webpack path). @solidjs/vite-plugin 3.0.0-next.44 peer-requires solid-js ^2.0.0-rc.9 and ships the rc.9 compiler.rc.9 changed
serverFunctionUrlto describe aGET()reference's own call (serverFunctionUrl(fn, ...args)) and moved the id-based form-post address toserverFunctionActionUrl/parseServerFunctionActionUrl(serverFunctionUrlreturns/_server/<id>, but the server function invocation actually fetches/_server/data/<id>, making serverFunctionUrl return value unusable for preloading聽solidjs/solid#3440); @tanstack/solid-start's server-function handler now uses those.Rsbuild apps:
@rsbuild/plugin-solid@2.0.0-rc.0hard-pins the rc.6 compiler, which emits the old delegated-event key (el.$$click) that the rc.9 runtime no longer reads (_$$click), so delegated handlers never fire. Until the plugin ships an rc.9-based release, override its@solidjs/compilerand@solidjs/babel-pluginto 2.0.0-rc.9 (the monorepo does this inpnpm-workspace.yaml).Updated dependencies [
0dc3a9e]:@tanstack/solid-router-ssr-query@2.0.0-rc.7
Patch Changes
#8467
0dc3a9e- Bump solid-js and @solidjs/web to ^2.0.0-rc.9 and @solidjs/vite-plugin to ^3.0.0-next.44 across the monorepo (with @solidjs/babel-plugin 2.0.0-rc.9 for the webpack path). @solidjs/vite-plugin 3.0.0-next.44 peer-requires solid-js ^2.0.0-rc.9 and ships the rc.9 compiler.rc.9 changed
serverFunctionUrlto describe aGET()reference's own call (serverFunctionUrl(fn, ...args)) and moved the id-based form-post address toserverFunctionActionUrl/parseServerFunctionActionUrl(serverFunctionUrlreturns/_server/<id>, but the server function invocation actually fetches/_server/data/<id>, making serverFunctionUrl return value unusable for preloading聽solidjs/solid#3440); @tanstack/solid-start's server-function handler now uses those.Rsbuild apps:
@rsbuild/plugin-solid@2.0.0-rc.0hard-pins the rc.6 compiler, which emits the old delegated-event key (el.$$click) that the rc.9 runtime no longer reads (_$$click), so delegated handlers never fire. Until the plugin ships an rc.9-based release, override its@solidjs/compilerand@solidjs/babel-pluginto 2.0.0-rc.9 (the monorepo does this inpnpm-workspace.yaml).@tanstack/solid-start@2.0.0-rc.9
Patch Changes
#8467
0dc3a9e- Bump solid-js and @solidjs/web to ^2.0.0-rc.9 and @solidjs/vite-plugin to ^3.0.0-next.44 across the monorepo (with @solidjs/babel-plugin 2.0.0-rc.9 for the webpack path). @solidjs/vite-plugin 3.0.0-next.44 peer-requires solid-js ^2.0.0-rc.9 and ships the rc.9 compiler.rc.9 changed
serverFunctionUrlto describe aGET()reference's own call (serverFunctionUrl(fn, ...args)) and moved the id-based form-post address toserverFunctionActionUrl/parseServerFunctionActionUrl(serverFunctionUrlreturns/_server/<id>, but the server function invocation actually fetches/_server/data/<id>, making serverFunctionUrl return value unusable for preloading聽solidjs/solid#3440); @tanstack/solid-start's server-function handler now uses those.Rsbuild apps:
@rsbuild/plugin-solid@2.0.0-rc.0hard-pins the rc.6 compiler, which emits the old delegated-event key (el.$$click) that the rc.9 runtime no longer reads (_$$click), so delegated handlers never fire. Until the plugin ships an rc.9-based release, override its@solidjs/compilerand@solidjs/babel-pluginto 2.0.0-rc.9 (the monorepo does this inpnpm-workspace.yaml).Updated dependencies [
0dc3a9e]:@tanstack/solid-start-client@2.0.0-rc.9
Patch Changes
#8467
0dc3a9e- Bump solid-js and @solidjs/web to ^2.0.0-rc.9 and @solidjs/vite-plugin to ^3.0.0-next.44 across the monorepo (with @solidjs/babel-plugin 2.0.0-rc.9 for the webpack path). @solidjs/vite-plugin 3.0.0-next.44 peer-requires solid-js ^2.0.0-rc.9 and ships the rc.9 compiler.rc.9 changed
serverFunctionUrlto describe aGET()reference's own call (serverFunctionUrl(fn, ...args)) and moved the id-based form-post address toserverFunctionActionUrl/parseServerFunctionActionUrl(serverFunctionUrlreturns/_server/<id>, but the server function invocation actually fetches/_server/data/<id>, making serverFunctionUrl return value unusable for preloading聽solidjs/solid#3440); @tanstack/solid-start's server-function handler now uses those.Rsbuild apps:
@rsbuild/plugin-solid@2.0.0-rc.0hard-pins the rc.6 compiler, which emits the old delegated-event key (el.$$click) that the rc.9 runtime no longer reads (_$$click), so delegated handlers never fire. Until the plugin ships an rc.9-based release, override its@solidjs/compilerand@solidjs/babel-pluginto 2.0.0-rc.9 (the monorepo does this inpnpm-workspace.yaml).Updated dependencies [
0dc3a9e]:@tanstack/solid-start-server@2.0.0-rc.9
Patch Changes
#8467
0dc3a9e- Bump solid-js and @solidjs/web to ^2.0.0-rc.9 and @solidjs/vite-plugin to ^3.0.0-next.44 across the monorepo (with @solidjs/babel-plugin 2.0.0-rc.9 for the webpack path). @solidjs/vite-plugin 3.0.0-next.44 peer-requires solid-js ^2.0.0-rc.9 and ships the rc.9 compiler.rc.9 changed
serverFunctionUrlto describe aGET()reference's own call (serverFunctionUrl(fn, ...args)) and moved the id-based form-post address toserverFunctionActionUrl/parseServerFunctionActionUrl(serverFunctionUrlreturns/_server/<id>, but the server function invocation actually fetches/_server/data/<id>, making serverFunctionUrl return value unusable for preloading聽solidjs/solid#3440); @tanstack/solid-start's server-function handler now uses those.Rsbuild apps:
@rsbuild/plugin-solid@2.0.0-rc.0hard-pins the rc.6 compiler, which emits the old delegated-event key (el.$$click) that the rc.9 runtime no longer reads (_$$click), so delegated handlers never fire. Until the plugin ships an rc.9-based release, override its@solidjs/compilerand@solidjs/babel-pluginto 2.0.0-rc.9 (the monorepo does this inpnpm-workspace.yaml).Updated dependencies [
0dc3a9e]: