[github-actions]

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/alpine-hotkeys@0.6.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/angular-hotkeys@0.17.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/ember-hotkeys@0.6.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/hotkeys@0.18.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

@tanstack/hotkeys-devtools@1.6.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/lit-hotkeys@0.18.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/octane-hotkeys@0.7.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/preact-hotkeys@0.17.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/react-hotkeys@0.17.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/solid-hotkeys@0.17.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/svelte-hotkeys@0.17.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/vue-hotkeys@0.17.0

Minor Changes

• #199 431094a - Hotkey hints now show only for hotkeys that can fire. useHotkeyHint and the other adapters' hint helpers return false unless a registration of the hotkey can fire: it's enabled, in an active scope, and, for a hotkey on an element, focus is inside that element. Hotkeys registered with enabled: false, hotkeys suspended by an exclusive scope, hotkeys on an element that doesn't have focus, and hotkeys that nothing registered no longer show hints. App hotkeys match their registrations by id, so custom hotkeys still work. To keep the old behavior, call matchesHeldModifiers, which still checks only held keys. The new HotkeyManager.hasActiveRegistration(hotkey) reports whether a hotkey or app hotkey has a registration that can fire.

  Add preventDefault: 'always'. A chord with this option still prevents the browser's action while it can't fire, because it's disabled or its scope is inactive or suspended. For example, a disabled Mod+S no longer opens the browser's Save dialog. It doesn't stop propagation, and it still skips typing in text fields. When another hotkey handles the key, that hotkey's options apply instead. Sequences treat 'always' as true. Set it in default options to apply it to every hotkey. We recommend it for most hotkeys; the sensible defaults guide explains when to leave it off, such as for Mod+C or Tab hotkeys you turn off to hand the key back to the browser. Devtools show always for these hotkeys.

  Registration views now have a status: 'active' when the hotkey is enabled and its scope is active, 'suspended' when its scope is inactive or suspended by an exclusive scope, and 'disabled' when it has enabled: false. To list only the hotkeys that are on, filter by status === 'active' instead of checking enabled and isScopeActive yourself.

  Each adapter has a new API that reads the hotkey manager's scope state and updates when scopes activate or release: useHotkeyScopesState in React, Preact, Vue, Ember, and Octane, createHotkeyScopesState in Solid and on Alpine's createHotkeysScope owner, injectHotkeyScopesState in Angular, getHotkeyScopesState in Svelte, and HotkeyScopesStateController in Lit.

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys@0.18.0

@tanstack/angular-hotkeys-devtools@0.3.1

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys-devtools@1.6.0

@tanstack/preact-hotkeys-devtools@0.11.1

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys-devtools@1.6.0

@tanstack/react-hotkeys-devtools@0.11.1

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys-devtools@1.6.0

@tanstack/solid-hotkeys-devtools@0.11.1

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys-devtools@1.6.0

@tanstack/svelte-hotkeys-devtools@0.3.1

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys-devtools@1.6.0

@tanstack/vue-hotkeys-devtools@0.11.1

Patch Changes

• Updated dependencies [431094a]:
  • @tanstack/hotkeys-devtools@1.6.0

[coderabbitai]

Important

Review skipped

Bot user detected.

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

Run configuration

• Source mode: Auto
• Repository: TanStack/hotkeys
• Branch: main
• File: .coderabbit.yaml
• Commit: 431094a
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 03b595af-ba0a-40cc-9b91-b8029938e5dc

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}