ci: Version Packages#475
Merged
Merged
Conversation
5fc4295 to
ae4feed
Compare
ae4feed to
adfb418
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
AlemTuzlak
approved these changes
Jun 24, 2026
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.
Releases
@tanstack/devtools-ui@0.6.0
Minor Changes
#477
ea3c674- fix: rename Soliduse*primitives tocreate*so React Compiler doesn't transform themThe devtools packages are written in Solid but used React-style naming (
useStyles,useTheme,useDevtoolsState, …) for their custom primitives. When an app enables React Compiler, the compiler matches theuse*naming convention and transforms/optimizes this Solid code as if it were React, breaking the panel (it is Solid JSX, not React).All custom Solid primitives in
@tanstack/devtools,@tanstack/devtools-ui, and@tanstack/devtools-a11yare renamed fromuse*tocreate*, and Solid's ownuseContext/@solid-primitivesuseKeyDownListare imported under non-usealiases (getContext,getKeyDownList).Breaking for
@tanstack/devtools-ui: the exporteduseThemeis renamed tocreateTheme.Patch Changes
7114ecd- FixCheckboxignoring controlledcheckedprop updates. It previously readcheckedinto internal state only once at mount, so it never reflected later prop changes when used as a controlled input (e.g. the devtools settings panel). It now reflects thecheckedprop whenever it is provided and falls back to internal state only when uncontrolled.@tanstack/devtools-event-client@0.5.0
Minor Changes
#471
b1ac893- The root export of@tanstack/devtools-event-clientnow resolves to a no-opoutside development (
process.env.NODE_ENV !== 'development'), so the realEventClientis tree-shaken out of production bundles by default.If you want devtools events to keep working in production, import the real
client from the new
@tanstack/devtools-event-client/productionsubpath, whichalways ships the real implementation. The public API is identical between the
two imports.
@tanstack/angular-devtools@0.0.7
Patch Changes
ea3c674]:@tanstack/devtools@0.12.5
Patch Changes
#477
ea3c674- fix: rename Soliduse*primitives tocreate*so React Compiler doesn't transform themThe devtools packages are written in Solid but used React-style naming (
useStyles,useTheme,useDevtoolsState, …) for their custom primitives. When an app enables React Compiler, the compiler matches theuse*naming convention and transforms/optimizes this Solid code as if it were React, breaking the panel (it is Solid JSX, not React).All custom Solid primitives in
@tanstack/devtools,@tanstack/devtools-ui, and@tanstack/devtools-a11yare renamed fromuse*tocreate*, and Solid's ownuseContext/@solid-primitivesuseKeyDownListare imported under non-usealiases (getContext,getKeyDownList).Breaking for
@tanstack/devtools-ui: the exporteduseThemeis renamed tocreateTheme.Updated dependencies [
7114ecd,ea3c674]:@tanstack/devtools-a11y@0.1.6
Patch Changes
#477
ea3c674- fix: rename Soliduse*primitives tocreate*so React Compiler doesn't transform themThe devtools packages are written in Solid but used React-style naming (
useStyles,useTheme,useDevtoolsState, …) for their custom primitives. When an app enables React Compiler, the compiler matches theuse*naming convention and transforms/optimizes this Solid code as if it were React, breaking the panel (it is Solid JSX, not React).All custom Solid primitives in
@tanstack/devtools,@tanstack/devtools-ui, and@tanstack/devtools-a11yare renamed fromuse*tocreate*, and Solid's ownuseContext/@solid-primitivesuseKeyDownListare imported under non-usealiases (getContext,getKeyDownList).Breaking for
@tanstack/devtools-ui: the exporteduseThemeis renamed tocreateTheme.Updated dependencies [
7114ecd,ea3c674]:@tanstack/devtools-client@0.0.8
Patch Changes
b1ac893]:@tanstack/devtools-vite@0.8.1
Patch Changes
@tanstack/preact-devtools@0.10.8
Patch Changes
ea3c674]:@tanstack/react-devtools@0.10.8
Patch Changes
ea3c674]:@tanstack/solid-devtools@0.8.8
Patch Changes
ea3c674]:@tanstack/svelte-devtools@0.1.1
Patch Changes
ea3c674]:@tanstack/vue-devtools@0.2.22
Patch Changes
ea3c674]:@tanstack/devtools-e2e@0.0.1
Patch Changes
b1ac893]:@tanstack/devtools-example-angular-a11y-devtools@0.0.6
Patch Changes
b1ac893,ea3c674]:@tanstack/devtools-example-angular-basic@0.0.6
Patch Changes
b1ac893]:@tanstack/devtools-example-angular-panel@0.0.7
Patch Changes
b1ac893,ea3c674]:@tanstack/devtools-example-angular-with-devtools@0.0.6
Patch Changes
b1ac893]: