ci: Version Packages - #495
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
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@0.14.0
Minor Changes
#492
a46d1f5- feat: arrange plugin panes in splits and stacked tabs, drag and resize them, and raise the limit to eighteenThe Plugins destination is now a workspace instead of a fixed row. Panes can sit side by side, above and below each other, or stacked as tabs in one group, and the arrangement is a tree that persists across reloads along with each pane's size and which tab is selected. Up to eighteen plugins can be open, up from three, because a stacked tab costs no space.
Drag a pane's tab onto the edge of another pane to split it, onto its middle to stack, or onto another tab bar to move it there. Drag the gutter between two panes to resize: one grows by exactly what the other loses, and neither can shrink below a readable minimum. Where the panel is too short to split without leaving an unreadable cell, the same drop becomes a stacked tab rather than being refused. The tab being carried follows the cursor, and a highlight shows where it will land.
The Plugins strip now lists only the plugins that are not open, so each plugin has exactly one control: its strip entry while closed, its pane tab once open. Entries can be dragged out of the strip to place a pane exactly where you want it instead of appending it, including onto an empty workspace, where it takes the whole area. The strip folds itself away once everything is open and returns when a plugin closes.
Every one of those actions has a keyboard equivalent, because the pointer gestures are suppressed while the panel is detached into a picture-in-picture window.
Enterpicks a pane up, the arrow keys choose where it goes,Enterdrops it andEscapeputs it back; gutters take arrow keys,Shift-arrow andHome/End, the same pattern the whole-panel resizer already used. Picking up and dropping is announced to screen readers.For plugin authors, two guarantees are now explicit. A pane's mount node is never removed from the document while the plugin is open, whatever the user does to the layout, so an
<iframe>will not reload and a<canvas>will not lose its context. Anddestroyis called exactly once, when the plugin closes, before the node is detached — not when a pane is moved, resized, or hidden by navigating to another destination.state.activePluginsinlocalStorageis superseded bystate.layout. Existing state is migrated on first read, reopening as a single group in the order it recorded, and an arrangement that cannot be read is repaired rather than throwing: unknown plugin ids are dropped, empty groups close up, and a wholly unusable entry falls back to reopening whatever plugins it can still identify.#492
a46d1f5- feat: apply TanStack branding and the compact Workbench layout across core, shared UI, and accessibility DevtoolsThe Workbench now separates chrome from canvas: the header and the secondary strips paint the brand surface and share one 16px gutter with the content below them. The palm emblem is inline SVG instead of a filtered raster, plugin destinations get a real empty state, and the Marketplace, SEO, and Settings destinations drop their competing accent colours in favour of the semantic theme.
The secondary strip gets a pull tab on its bottom edge that folds the strip away behind the header, leaving the panel height and the destination content untouched. It only appears on destinations that have a strip.
The SEO tab's
<head>watcher no longer reports<style>tags. It observes attributes and character data across the whole<head>subtree, and a CSS-in-JS library rewrites a<style>tag there on every render — so an SEO analysis triggered a re-render, the re-render emitted CSS, and the CSS triggered another analysis. Stylesheets carry no SEO metadata, so they are filtered out.Fixes along the way: the resize handle had grown to 24px and sat on top of the header, so a press aimed at a header button started a resize instead of clicking; the Marketplace settings drawer was
position: fixedand covered the host page instead of the Workbench; the floating trigger lost its brand fill on hover and its transition was overridden away; the "New" ribbon on a plugin card overlapped the card icon; scroll gestures inside the panel chained on to the host page; and the hotkey editor showed each shortcut's description as its heading and never rendered its title.Patch Changes
a46d1f5]:@tanstack/devtools-a11y@0.2.0
Minor Changes
#492
a46d1f5- feat: apply TanStack branding and the compact Workbench layout across core, shared UI, and accessibility DevtoolsThe Workbench now separates chrome from canvas: the header and the secondary strips paint the brand surface and share one 16px gutter with the content below them. The palm emblem is inline SVG instead of a filtered raster, plugin destinations get a real empty state, and the Marketplace, SEO, and Settings destinations drop their competing accent colours in favour of the semantic theme.
The secondary strip gets a pull tab on its bottom edge that folds the strip away behind the header, leaving the panel height and the destination content untouched. It only appears on destinations that have a strip.
The SEO tab's
<head>watcher no longer reports<style>tags. It observes attributes and character data across the whole<head>subtree, and a CSS-in-JS library rewrites a<style>tag there on every render — so an SEO analysis triggered a re-render, the re-render emitted CSS, and the CSS triggered another analysis. Stylesheets carry no SEO metadata, so they are filtered out.Fixes along the way: the resize handle had grown to 24px and sat on top of the header, so a press aimed at a header button started a resize instead of clicking; the Marketplace settings drawer was
position: fixedand covered the host page instead of the Workbench; the floating trigger lost its brand fill on hover and its transition was overridden away; the "New" ribbon on a plugin card overlapped the card icon; scroll gestures inside the panel chained on to the host page; and the hotkey editor showed each shortcut's description as its heading and never rendered its title.Patch Changes
a46d1f5]:@tanstack/devtools-ui@0.7.0
Minor Changes
#492
a46d1f5- feat: apply TanStack branding and the compact Workbench layout across core, shared UI, and accessibility DevtoolsThe Workbench now separates chrome from canvas: the header and the secondary strips paint the brand surface and share one 16px gutter with the content below them. The palm emblem is inline SVG instead of a filtered raster, plugin destinations get a real empty state, and the Marketplace, SEO, and Settings destinations drop their competing accent colours in favour of the semantic theme.
The secondary strip gets a pull tab on its bottom edge that folds the strip away behind the header, leaving the panel height and the destination content untouched. It only appears on destinations that have a strip.
The SEO tab's
<head>watcher no longer reports<style>tags. It observes attributes and character data across the whole<head>subtree, and a CSS-in-JS library rewrites a<style>tag there on every render — so an SEO analysis triggered a re-render, the re-render emitted CSS, and the CSS triggered another analysis. Stylesheets carry no SEO metadata, so they are filtered out.Fixes along the way: the resize handle had grown to 24px and sat on top of the header, so a press aimed at a header button started a resize instead of clicking; the Marketplace settings drawer was
position: fixedand covered the host page instead of the Workbench; the floating trigger lost its brand fill on hover and its transition was overridden away; the "New" ribbon on a plugin card overlapped the card icon; scroll gestures inside the panel chained on to the host page; and the hotkey editor showed each shortcut's description as its heading and never rendered its title.@tanstack/angular-devtools@0.0.9
Patch Changes
a46d1f5,a46d1f5]:@tanstack/preact-devtools@0.10.10
Patch Changes
a46d1f5,a46d1f5]:@tanstack/react-devtools@0.10.10
Patch Changes
a46d1f5,a46d1f5]:@tanstack/solid-devtools@0.8.10
Patch Changes
a46d1f5,a46d1f5]:@tanstack/svelte-devtools@0.1.3
Patch Changes
a46d1f5,a46d1f5]:@tanstack/vue-devtools@0.2.24
Patch Changes
a46d1f5,a46d1f5]:@tanstack/devtools-example-angular-a11y-devtools@0.0.8
Patch Changes
a46d1f5]:@tanstack/devtools-example-angular-basic@0.0.8
Patch Changes
@tanstack/devtools-example-angular-panel@0.0.9
Patch Changes
a46d1f5,a46d1f5]:@tanstack/devtools-example-angular-with-devtools@0.0.8
Patch Changes