Skip to content

ci: Version Packages - #224

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

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/hotkeys@0.24.0

Minor Changes

  • #225 b5e429a - Run element-target hotkeys after the framework's own key handlers in React, Svelte, Solid, and Octane. An onKeyDown handler inside the target, such as an autocomplete that closes on Escape, now runs first and can stop the hotkey. Before, the hotkey ran first and its default stopPropagation kept the key from those handlers.

    These adapters set the new afterDelegatedHandlers option, so an element target listens on its document, or on its closed shadow root. Framework handlers outside the target also run before the hotkey now. In Solid, a stop by an onKeyDown handler also skips document hotkeys, even when the hotkey registered before the first component that uses onKeyDown loaded.

  • #228 d3adb24 - Add the ignoreDefaultPrevented option. A hotkey with it skips a key press that another listener already handled with preventDefault(), such as a Radix UI or shadcn/ui dropdown closing on Escape. A hotkey's own preventDefault doesn't count. Set it in a provider's default options to apply it to every hotkey.

  • #228 d3adb24 - Fire a keyup chord when the user releases its key or one of its modifiers, whichever comes first. Before, releasing the modifier first meant the chord never fired, and on macOS a keyup Mod chord never fired at all, because macOS sends no keyup for a key released while Command is held.

    A keyup chord now also prevents its keydown's default action, so a keyup Mod+S stops the browser's Save dialog. Set preventDefault: false to let the browser act on the keydown.

  • #228 d3adb24 - Leave Escape to an open modal <dialog> or a popover that closes on Escape, which is any popover except popover="manual". While one is open, hotkeys outside it skip Escape, so the browser closes it instead of a global Escape hotkey keeping it open. A hotkey targeted at the dialog or popover, or at an element inside it, still receives Escape.

Patch Changes

  • #228 d3adb24 - Fix hotkeys in a scope that stopped firing when a provider with the same scope mounted inside it. The inner provider replaced the scope's parent with the scope itself, so the scope dropped out of an exclusive ancestor such as a dialog.

  • #223 04c7445 - Fix formatForDisplay throwing during server rendering on runtimes without process, such as Cloudflare Workers.

@tanstack/octane-hotkeys@0.11.0

Minor Changes

  • #225 b5e429a - Run element-target hotkeys after the framework's own key handlers in React, Svelte, Solid, and Octane. An onKeyDown handler inside the target, such as an autocomplete that closes on Escape, now runs first and can stop the hotkey. Before, the hotkey ran first and its default stopPropagation kept the key from those handlers.

    These adapters set the new afterDelegatedHandlers option, so an element target listens on its document, or on its closed shadow root. Framework handlers outside the target also run before the hotkey now. In Solid, a stop by an onKeyDown handler also skips document hotkeys, even when the hotkey registered before the first component that uses onKeyDown loaded.

Patch Changes

@tanstack/react-hotkeys@0.22.0

Minor Changes

  • #225 b5e429a - Run element-target hotkeys after the framework's own key handlers in React, Svelte, Solid, and Octane. An onKeyDown handler inside the target, such as an autocomplete that closes on Escape, now runs first and can stop the hotkey. Before, the hotkey ran first and its default stopPropagation kept the key from those handlers.

    These adapters set the new afterDelegatedHandlers option, so an element target listens on its document, or on its closed shadow root. Framework handlers outside the target also run before the hotkey now. In Solid, a stop by an onKeyDown handler also skips document hotkeys, even when the hotkey registered before the first component that uses onKeyDown loaded.

Patch Changes

@tanstack/solid-hotkeys@0.21.0

Minor Changes

  • #225 b5e429a - Run element-target hotkeys after the framework's own key handlers in React, Svelte, Solid, and Octane. An onKeyDown handler inside the target, such as an autocomplete that closes on Escape, now runs first and can stop the hotkey. Before, the hotkey ran first and its default stopPropagation kept the key from those handlers.

    These adapters set the new afterDelegatedHandlers option, so an element target listens on its document, or on its closed shadow root. Framework handlers outside the target also run before the hotkey now. In Solid, a stop by an onKeyDown handler also skips document hotkeys, even when the hotkey registered before the first component that uses onKeyDown loaded.

Patch Changes

@tanstack/svelte-hotkeys@0.21.0

Minor Changes

  • #225 b5e429a - Run element-target hotkeys after the framework's own key handlers in React, Svelte, Solid, and Octane. An onKeyDown handler inside the target, such as an autocomplete that closes on Escape, now runs first and can stop the hotkey. Before, the hotkey ran first and its default stopPropagation kept the key from those handlers.

    These adapters set the new afterDelegatedHandlers option, so an element target listens on its document, or on its closed shadow root. Framework handlers outside the target also run before the hotkey now. In Solid, a stop by an onKeyDown handler also skips document hotkeys, even when the hotkey registered before the first component that uses onKeyDown loaded.

Patch Changes

@tanstack/alpine-hotkeys@0.11.1

Patch Changes

@tanstack/angular-hotkeys@0.21.1

Patch Changes

@tanstack/angular-hotkeys-devtools@0.5.1

Patch Changes

  • Updated dependencies []:
    • @tanstack/hotkeys-devtools@1.8.1

@tanstack/ember-hotkeys@0.10.1

Patch Changes

@tanstack/hotkeys-devtools@1.8.1

Patch Changes

@tanstack/lit-hotkeys@0.22.1

Patch Changes

@tanstack/preact-hotkeys@0.20.1

Patch Changes

@tanstack/preact-hotkeys-devtools@0.13.1

Patch Changes

  • Updated dependencies []:
    • @tanstack/hotkeys-devtools@1.8.1

@tanstack/react-hotkeys-devtools@0.14.1

Patch Changes

  • Updated dependencies []:
    • @tanstack/hotkeys-devtools@1.8.1

@tanstack/solid-hotkeys-devtools@0.13.1

Patch Changes

  • Updated dependencies []:
    • @tanstack/hotkeys-devtools@1.8.1

@tanstack/svelte-hotkeys-devtools@0.5.1

Patch Changes

  • Updated dependencies []:
    • @tanstack/hotkeys-devtools@1.8.1

@tanstack/vue-hotkeys@0.21.1

Patch Changes

@tanstack/vue-hotkeys-devtools@0.13.1

Patch Changes

  • Updated dependencies []:
    • @tanstack/hotkeys-devtools@1.8.1

@coderabbitai

coderabbitai Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 4081bd8 to 793f8db Compare November 2, 2026 00:17
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 793f8db to 5dddb72 Compare November 2, 2026 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants