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/dialog@0.2.1

Patch Changes

• #36 827c079 Thanks @ivanbanov! - Ship SPEC.md and the TypeScript sources in the published package, alongside
  the built dist.

  The tarball used to carry dist and README.md only, so the two things you
  actually want when a behavior surprises you — the spec that defines the contract
  and the code that implements it — were reachable only by finding the repo and
  guessing which tag matches the installed version. Both now sit in
  node_modules/<pkg>/, pinned to the exact version installed.

  Nothing about resolution changes: publishConfig still points main, types,
  and exports at dist, and the sources are inert payload — read them, don't
  import them.

• Updated dependencies [827c079]:

  • @dunky.dev/controllable@0.1.1

@dunky.dev/controllable@0.1.1

Patch Changes

• #36 827c079 Thanks @ivanbanov! - Ship SPEC.md and the TypeScript sources in the published package, alongside
  the built dist.

  The tarball used to carry dist and README.md only, so the two things you
  actually want when a behavior surprises you — the spec that defines the contract
  and the code that implements it — were reachable only by finding the repo and
  guessing which tag matches the installed version. Both now sit in
  node_modules/<pkg>/, pinned to the exact version installed.

  Nothing about resolution changes: publishConfig still points main, types,
  and exports at dist, and the sources are inert payload — read them, don't
  import them.

@dunky.dev/overlay@0.1.1

Patch Changes

• #36 827c079 Thanks @ivanbanov! - Ship SPEC.md and the TypeScript sources in the published package, alongside
  the built dist.

  The tarball used to carry dist and README.md only, so the two things you
  actually want when a behavior surprises you — the spec that defines the contract
  and the code that implements it — were reachable only by finding the repo and
  guessing which tag matches the installed version. Both now sit in
  node_modules/<pkg>/, pinned to the exact version installed.

  Nothing about resolution changes: publishConfig still points main, types,
  and exports at dist, and the sources are inert payload — read them, don't
  import them.

@dunky.dev/dom-focus-trap@0.1.1

Patch Changes

• #36 827c079 Thanks @ivanbanov! - Ship SPEC.md and the TypeScript sources in the published package, alongside
  the built dist.

  The tarball used to carry dist and README.md only, so the two things you
  actually want when a behavior surprises you — the spec that defines the contract
  and the code that implements it — were reachable only by finding the repo and
  guessing which tag matches the installed version. Both now sit in
  node_modules/<pkg>/, pinned to the exact version installed.

  Nothing about resolution changes: publishConfig still points main, types,
  and exports at dist, and the sources are inert payload — read them, don't
  import them.

@dunky.dev/dom-navigation@0.1.1

Patch Changes

• #36 827c079 Thanks @ivanbanov! - Ship SPEC.md and the TypeScript sources in the published package, alongside
  the built dist.

  The tarball used to carry dist and README.md only, so the two things you
  actually want when a behavior surprises you — the spec that defines the contract
  and the code that implements it — were reachable only by finding the repo and
  guessing which tag matches the installed version. Both now sit in
  node_modules/<pkg>/, pinned to the exact version installed.

  Nothing about resolution changes: publishConfig still points main, types,
  and exports at dist, and the sources are inert payload — read them, don't
  import them.

@dunky.dev/dom-overlay@0.1.1

Patch Changes

• #32 548ef7c Thanks @ivanbanov! - Anchor the overlay layer stack and the scroll-lock registry on a realm-global
  keyed by Symbol.for, so they survive the module being loaded more than once in
  a single page (duplicate bundles in a monorepo or micro-frontend).

  Both were plain module-level singletons. When a bundler ships two copies of the
  module — a common monorepo/micro-frontend hazard — each copy got its own stack
  and its own lock registry, so their "which layer is topmost" and "is the page
  still locked" decisions drifted apart: Escape or an outside press could dismiss
  the wrong dialog in a nested stack, and scroll lock could double-lock or leak.
  Radix hit the same class of bug with its focus-scope stack
  (Nested Popover in Dialog does not focus (focus scope stack in a monorepo) radix-ui/primitives#2815).

  The shared state now resolves through a well-known global symbol, so every
  duplicate copy rendezvous on the same instance. It is resolved lazily on first
  use, so the packages keep their sideEffects: false contract (no import-time
  global write). No API change.

• #36 827c079 Thanks @ivanbanov! - Ship SPEC.md and the TypeScript sources in the published package, alongside
  the built dist.

  The tarball used to carry dist and README.md only, so the two things you
  actually want when a behavior surprises you — the spec that defines the contract
  and the code that implements it — were reachable only by finding the repo and
  guessing which tag matches the installed version. Both now sit in
  node_modules/<pkg>/, pinned to the exact version installed.

  Nothing about resolution changes: publishConfig still points main, types,
  and exports at dist, and the sources are inert payload — read them, don't
  import them.

• Updated dependencies [827c079]:

  • @dunky.dev/overlay@0.1.1

@dunky.dev/dom-scroll-lock@0.1.1

Patch Changes

• #32 548ef7c Thanks @ivanbanov! - Anchor the overlay layer stack and the scroll-lock registry on a realm-global
  keyed by Symbol.for, so they survive the module being loaded more than once in
  a single page (duplicate bundles in a monorepo or micro-frontend).

  Both were plain module-level singletons. When a bundler ships two copies of the
  module — a common monorepo/micro-frontend hazard — each copy got its own stack
  and its own lock registry, so their "which layer is topmost" and "is the page
  still locked" decisions drifted apart: Escape or an outside press could dismiss
  the wrong dialog in a nested stack, and scroll lock could double-lock or leak.
  Radix hit the same class of bug with its focus-scope stack
  (Nested Popover in Dialog does not focus (focus scope stack in a monorepo) radix-ui/primitives#2815).

  The shared state now resolves through a well-known global symbol, so every
  duplicate copy rendezvous on the same instance. It is resolved lazily on first
  use, so the packages keep their sideEffects: false contract (no import-time
  global write). No API change.

• #36 827c079 Thanks @ivanbanov! - Ship SPEC.md and the TypeScript sources in the published package, alongside
  the built dist.

  The tarball used to carry dist and README.md only, so the two things you
  actually want when a behavior surprises you — the spec that defines the contract
  and the code that implements it — were reachable only by finding the repo and
  guessing which tag matches the installed version. Both now sit in
  node_modules/<pkg>/, pinned to the exact version installed.

  Nothing about resolution changes: publishConfig still points main, types,
  and exports at dist, and the sources are inert payload — read them, don't
  import them.

@dunky.dev/react-dialog@0.2.1

Patch Changes

• #36 827c079 Thanks @ivanbanov! - Ship SPEC.md and the TypeScript sources in the published package, alongside
  the built dist.

  The tarball used to carry dist and README.md only, so the two things you
  actually want when a behavior surprises you — the spec that defines the contract
  and the code that implements it — were reachable only by finding the repo and
  guessing which tag matches the installed version. Both now sit in
  node_modules/<pkg>/, pinned to the exact version installed.

  Nothing about resolution changes: publishConfig still points main, types,
  and exports at dist, and the sources are inert payload — read them, don't
  import them.

• Updated dependencies [548ef7c, 827c079]:

  • @dunky.dev/dom-overlay@0.1.1
  • @dunky.dev/dialog@0.2.1
  • @dunky.dev/dom-navigation@0.1.1
  • @dunky.dev/react-use-focus-trap@0.1.1
  • @dunky.dev/react-use-scroll-lock@0.1.1

@dunky.dev/react-use-focus-trap@0.1.1

Patch Changes

• #36 827c079 Thanks @ivanbanov! - Ship SPEC.md and the TypeScript sources in the published package, alongside
  the built dist.

  The tarball used to carry dist and README.md only, so the two things you
  actually want when a behavior surprises you — the spec that defines the contract
  and the code that implements it — were reachable only by finding the repo and
  guessing which tag matches the installed version. Both now sit in
  node_modules/<pkg>/, pinned to the exact version installed.

  Nothing about resolution changes: publishConfig still points main, types,
  and exports at dist, and the sources are inert payload — read them, don't
  import them.

• Updated dependencies [827c079]:

  • @dunky.dev/dom-focus-trap@0.1.1

@dunky.dev/react-use-scroll-lock@0.1.1

Patch Changes

• #36 827c079 Thanks @ivanbanov! - Ship SPEC.md and the TypeScript sources in the published package, alongside
  the built dist.

  The tarball used to carry dist and README.md only, so the two things you
  actually want when a behavior surprises you — the spec that defines the contract
  and the code that implements it — were reachable only by finding the repo and
  guessing which tag matches the installed version. Both now sit in
  node_modules/<pkg>/, pinned to the exact version installed.

  Nothing about resolution changes: publishConfig still points main, types,
  and exports at dist, and the sources are inert payload — read them, don't
  import them.

• Updated dependencies [548ef7c, 827c079]:

  • @dunky.dev/dom-scroll-lock@0.1.1