chore(release): version packages

[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

@dunky.dev/native-state-machine@0.3.0

Minor Changes

• #49 521440e Thanks @ivanbanov! - Breaking: remove the ComponentEffects<M, P> type alias. It was a pure
  alias for ComponentEffect<M, P>[] — a second public name for the same
  concept, with no semantics of its own (it can't enforce the static-list rule
  it documented). One concept, one export.

  Migration is mechanical:

  -import { type ComponentEffects } from '@dunky.dev/react-state-machine'
  +import { type ComponentEffect } from '@dunky.dev/react-state-machine'
  
  -const tooltipEffects: ComponentEffects<TooltipMachine, TooltipProps> = [trackEscape]
  +const tooltipEffects: ComponentEffect<TooltipMachine, TooltipProps>[] = [trackEscape]

• #43 58f9d7e Thanks @ivanbanov! - Rename the framework adapters back to a *-state-machine substrate-prefix convention.

  We tried the state-machine-* suffix convention (see the previous rename) to
  keep the whole @dunky.dev/* scope alphabetically consistent. In practice it
  proved ergonomically wrong once you picture it scaled to more than one
  package family:

  suffix (tried):        prefix (this change):
  button-react            react-button
  dropdown-react          react-dropdown
  state-machine-react     react-state-machine
  

  Picture browsing npm under @dunky.dev/react-* — every React package for
  this scope, together, in one look. That's the whole point of an org scope:
  someone building a React app should be able to find everything React-related
  under @dunky.dev/react-*. The suffix form breaks that; button-react,
  dropdown-react, and state-machine-react don't show up together anywhere,
  because "react" isn't what they're named by.

  It reads backwards at the import site too —
  import { useMachine } from '@dunky.dev/state-machine-react' names the
  library before the framework, when every other adapter a React codebase
  imports (react-redux, react-query, react-hook-form) names the framework
  first.

  • @dunky.dev/state-machine-react → @dunky.dev/react-state-machine
  • @dunky.dev/state-machine-native → @dunky.dev/native-state-machine
  • @dunky.dev/state-machine-opentui → @dunky.dev/opentui-state-machine

  The previous suffix-named packages are deprecated on npm in favor of these.

  - import { useMachine } from '@dunky.dev/state-machine-react'
  + import { useMachine } from '@dunky.dev/react-state-machine'

  @dunky.dev/state-machine (core), @dunky.dev/state-machine-utils, and @dunky.dev/state-machine-bindings are unchanged — they aren't tied to one substrate, so the prefix convention doesn't apply to them.

Patch Changes

• Updated dependencies [521440e, 58f9d7e]:
  • @dunky.dev/react-state-machine@0.3.0
  • @dunky.dev/state-machine@0.3.0
  • @dunky.dev/state-machine-utils@0.3.0

@dunky.dev/opentui-state-machine@0.3.0

Minor Changes

• #43 58f9d7e Thanks @ivanbanov! - Rename the framework adapters back to a *-state-machine substrate-prefix convention.

  We tried the state-machine-* suffix convention (see the previous rename) to
  keep the whole @dunky.dev/* scope alphabetically consistent. In practice it
  proved ergonomically wrong once you picture it scaled to more than one
  package family:

  suffix (tried):        prefix (this change):
  button-react            react-button
  dropdown-react          react-dropdown
  state-machine-react     react-state-machine
  

  Picture browsing npm under @dunky.dev/react-* — every React package for
  this scope, together, in one look. That's the whole point of an org scope:
  someone building a React app should be able to find everything React-related
  under @dunky.dev/react-*. The suffix form breaks that; button-react,
  dropdown-react, and state-machine-react don't show up together anywhere,
  because "react" isn't what they're named by.

  It reads backwards at the import site too —
  import { useMachine } from '@dunky.dev/state-machine-react' names the
  library before the framework, when every other adapter a React codebase
  imports (react-redux, react-query, react-hook-form) names the framework
  first.

  • @dunky.dev/state-machine-react → @dunky.dev/react-state-machine
  • @dunky.dev/state-machine-native → @dunky.dev/native-state-machine
  • @dunky.dev/state-machine-opentui → @dunky.dev/opentui-state-machine

  The previous suffix-named packages are deprecated on npm in favor of these.

  - import { useMachine } from '@dunky.dev/state-machine-react'
  + import { useMachine } from '@dunky.dev/react-state-machine'

  @dunky.dev/state-machine (core), @dunky.dev/state-machine-utils, and @dunky.dev/state-machine-bindings are unchanged — they aren't tied to one substrate, so the prefix convention doesn't apply to them.

Patch Changes

• Updated dependencies []:
  • @dunky.dev/state-machine-utils@0.3.0

@dunky.dev/react-state-machine@0.3.0

Minor Changes

• #49 521440e Thanks @ivanbanov! - Breaking: remove the ComponentEffects<M, P> type alias. It was a pure
  alias for ComponentEffect<M, P>[] — a second public name for the same
  concept, with no semantics of its own (it can't enforce the static-list rule
  it documented). One concept, one export.

  Migration is mechanical:

  -import { type ComponentEffects } from '@dunky.dev/react-state-machine'
  +import { type ComponentEffect } from '@dunky.dev/react-state-machine'
  
  -const tooltipEffects: ComponentEffects<TooltipMachine, TooltipProps> = [trackEscape]
  +const tooltipEffects: ComponentEffect<TooltipMachine, TooltipProps>[] = [trackEscape]

• #43 58f9d7e Thanks @ivanbanov! - Rename the framework adapters back to a *-state-machine substrate-prefix convention.

  We tried the state-machine-* suffix convention (see the previous rename) to
  keep the whole @dunky.dev/* scope alphabetically consistent. In practice it
  proved ergonomically wrong once you picture it scaled to more than one
  package family:

  suffix (tried):        prefix (this change):
  button-react            react-button
  dropdown-react          react-dropdown
  state-machine-react     react-state-machine
  

  Picture browsing npm under @dunky.dev/react-* — every React package for
  this scope, together, in one look. That's the whole point of an org scope:
  someone building a React app should be able to find everything React-related
  under @dunky.dev/react-*. The suffix form breaks that; button-react,
  dropdown-react, and state-machine-react don't show up together anywhere,
  because "react" isn't what they're named by.

  It reads backwards at the import site too —
  import { useMachine } from '@dunky.dev/state-machine-react' names the
  library before the framework, when every other adapter a React codebase
  imports (react-redux, react-query, react-hook-form) names the framework
  first.

  • @dunky.dev/state-machine-react → @dunky.dev/react-state-machine
  • @dunky.dev/state-machine-native → @dunky.dev/native-state-machine
  • @dunky.dev/state-machine-opentui → @dunky.dev/opentui-state-machine

  The previous suffix-named packages are deprecated on npm in favor of these.

  - import { useMachine } from '@dunky.dev/state-machine-react'
  + import { useMachine } from '@dunky.dev/react-state-machine'

  @dunky.dev/state-machine (core), @dunky.dev/state-machine-utils, and @dunky.dev/state-machine-bindings are unchanged — they aren't tied to one substrate, so the prefix convention doesn't apply to them.

Patch Changes

• Updated dependencies []:
  • @dunky.dev/state-machine@0.3.0
  • @dunky.dev/state-machine-utils@0.3.0

@dunky.dev/state-machine@0.3.0

@dunky.dev/state-machine-bindings@0.3.0

@dunky.dev/state-machine-utils@0.3.0

benchmark@0.1.3

Patch Changes

• Updated dependencies [521440e, 58f9d7e]:
  • @dunky.dev/react-state-machine@0.3.0
  • @dunky.dev/state-machine@0.3.0

benchmark-demo@0.1.4

Patch Changes

• Updated dependencies []:
  • @dunky.dev/state-machine@0.3.0

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dunky-state-machine	Ready	Preview, Comment	Jul 14, 2026 4:26pm