ci: Version Packages - #8119
Conversation
github-actions
Bot
added
package: react-router
package: router-core
package: router-plugin
package: router-generator
package: router-cli
package: solid-router
package: router-vite-plugin
package: react-start-server
package: react-start
package: react-start-client
package: solid-start-client
package: solid-start-server
package: solid-start
package: start-plugin-core
package: start-server-core
package: start-client-core
package: start-static-server-functions
package: start-storage-context
package: vue-router
package: vue-start-client
package: vue-start
package: vue-start-server
package: react-start-rsc
labels
|
View your CI Pipeline Execution ↗ for commit 73d9857
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
Bundle Size BenchmarksThis pull request does not affect bundle size in any measured scenario. |
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the failing E2E task and determined it is unrelated to the PR changes. The error is a port conflict (EADDRINUSE 127.0.0.1:36167) caused by another process occupying the port on the CI runner at the time the test server tried to start. Since this PR only bumps package versions with no source or config changes, a rerun should resolve the issue.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
Merging this PR will regress 0 benchmarks
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | Memory | mem server error-paths error (vue) |
2,335.7 KB | 942.5 KB | ×2.5 |
| ⚡ | Simulation | client-links navigation loop (vue) |
587.9 ms | 384.5 ms | +52.89% |
| ⚡ | Simulation | client-route-tree-scale navigation loop (vue) |
230.2 ms | 200.8 ms | +14.64% |
| ⚡ | Simulation | client-side navigation loop (vue) |
241.1 ms | 213.2 ms | +13.09% |
| ⚡ | Simulation | client-search-params navigation loop (vue) |
232.5 ms | 206.6 ms | +12.57% |
| ⚡ | Simulation | client-control-flow navigation loop (vue) |
118.2 ms | 105.5 ms | +12.08% |
| ⚡ | Simulation | client-async-pipeline navigation loop (vue) |
133.9 ms | 122.3 ms | +9.46% |
| ⚡ | Simulation | client-head navigation loop (vue) |
312.5 ms | 288.3 ms | +8.4% |
| ⚡ | Simulation | client-loaders navigation loop (vue) |
168.2 ms | 156.1 ms | +7.75% |
| ⚡ | Simulation | client-rewrites navigation loop (vue) |
217.6 ms | 203.3 ms | +7.07% |
| ⚡ | Simulation | client-preload interaction loop (vue) |
213.2 ms | 199.3 ms | +6.98% |
| ⚡ | Simulation | client-history navigation loop (vue) |
164 ms | 154 ms | +6.5% |
| ⚡ | Simulation | client-nested-params navigation loop (vue) |
340.2 ms | 319.7 ms | +6.41% |
| ⚡ | Memory | mem server error-paths error (react) |
1,035.4 KB | 974.2 KB | +6.29% |
| ⚡ | Simulation | client-head navigation loop (react) |
209.8 ms | 203 ms | +3.35% |
| ⚡ | Memory | mem server serialization-payload (vue) |
4.5 MB | 4.4 MB | +3.21% |
| 👁 | Memory | mem server error-paths not-found (solid) |
929.4 KB | 592.3 KB | +56.93% |
| 👁 | Memory | mem server peak-large-page (solid) |
1.1 MB | 1.2 MB | -8.08% |
| 👁 | Simulation | ssr global-mw document (vue) |
905.3 ms | 969 ms | -6.57% |
| 👁 | Memory | mem client navigation-churn (vue) |
1.6 MB | 1.6 MB | +5.06% |
| ... | ... | ... | ... | ... | ... |
ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing changeset-release/main (73d9857) with main (a1c3674)1
Footnotes
1 participant
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.
Releases
@tanstack/react-router@1.170.31
Patch Changes
3e016ac]:@tanstack/react-start@1.168.48
Patch Changes
@tanstack/react-start-client@1.168.29
Patch Changes
3e016ac]:@tanstack/react-start-rsc@0.1.47
Patch Changes
3e016ac]:@tanstack/react-start-server@1.167.36
Patch Changes
3e016ac]:@tanstack/router-cli@1.167.32
Patch Changes
@tanstack/router-core@1.171.26
Patch Changes
3e016ac- optimize buildLocation path resolution perf(router-core): optimize buildLocation path resolution #8108skip building search validation when disabled perf(router-core): skip disabled search validation #8112
skip location state sharing when impossible perf(router-core): skip impossible state sharing #8110
fix cache hits for mask resolution when entry is null perf(router-core): cache route mask misses #8111
@tanstack/router-generator@1.167.32
Patch Changes
3e016ac]:@tanstack/router-plugin@1.168.34
Patch Changes
3e016ac]:@tanstack/router-vite-plugin@1.167.34
Patch Changes
@tanstack/solid-router@1.170.29
Patch Changes
3e016ac]:@tanstack/solid-start@1.168.46
Patch Changes
@tanstack/solid-start-client@1.168.28
Patch Changes
3e016ac]:@tanstack/solid-start-server@1.167.35
Patch Changes
3e016ac]:@tanstack/start-client-core@1.170.26
Patch Changes
3e016ac]:@tanstack/start-plugin-core@1.171.38
Patch Changes
3e016ac]:@tanstack/start-server-core@1.169.30
Patch Changes
3e016ac]:@tanstack/start-static-server-functions@1.167.31
Patch Changes
@tanstack/start-storage-context@1.167.28
Patch Changes
3e016ac]:@tanstack/vue-router@1.170.28
Patch Changes
3e016ac]:@tanstack/vue-start@1.168.45
Patch Changes
@tanstack/vue-start-client@1.167.31
Patch Changes
3e016ac]:@tanstack/vue-start-server@1.167.35
Patch Changes
3e016ac]: