From 24c39135e6e95a29b8fd49c4582c0cca77773fc0 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Mon, 17 Aug 2026 12:30:59 +0000
Subject: [PATCH] chore(release): version packages

---
 .changeset/content-role-dialog-element.md | 7 -------
 packages/react/dialog/CHANGELOG.md        | 8 ++++++++
 packages/react/dialog/package.json        | 2 +-
 3 files changed, 9 insertions(+), 8 deletions(-)
 delete mode 100644 .changeset/content-role-dialog-element.md

diff --git a/.changeset/content-role-dialog-element.md b/.changeset/content-role-dialog-element.md
deleted file mode 100644
index cd5ffd3..0000000
--- a/.changeset/content-role-dialog-element.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@dunky.dev/react-dialog': minor
----
-
-`Dialog.Content` now renders a `<div>` carrying the `dialog` (or `alertdialog`) role instead of the native `<dialog>` element. Consumers styling `dialog { ... }` should target the part directly (or its role), and a forwarded ref is now an `HTMLDivElement`; `...props` accept `ComponentProps<'div'>`.
-
-The dialog window is the initial focus target — focusable in script, out of the tab order — which needs `tabindex="-1"`, and HTML states that [the `tabindex` attribute must not be specified on `dialog` elements](https://html.spec.whatwg.org/multipage/interactive-elements.html#the-dialog-element). The native element would only pay off through `showModal()`, and this contract deliberately keeps modality, dismissal, and focus in the core machine rather than splitting authority with the browser's built-in behavior — so the element brought nothing but a conformance violation. Nothing about the exposed semantics changes: the same role, `aria-modal`, name, description, and focus behavior as before. UA `<dialog>` resets (`position: static`, `border: none`) are no longer needed in consumer styles.
diff --git a/packages/react/dialog/CHANGELOG.md b/packages/react/dialog/CHANGELOG.md
index d78ac99..d5ccb31 100644
--- a/packages/react/dialog/CHANGELOG.md
+++ b/packages/react/dialog/CHANGELOG.md
@@ -1,5 +1,13 @@
 # @dunky.dev/react-dialog
 
+## 0.3.0
+
+### Minor Changes
+
+- [#40](https://github.com/dunky-dev/ui/pull/40) [`148ee66`](https://github.com/dunky-dev/ui/commit/148ee66481f70852734a77814643814af5b339fc) Thanks [@ivanbanov](https://github.com/ivanbanov)! - `Dialog.Content` now renders a `<div>` carrying the `dialog` (or `alertdialog`) role instead of the native `<dialog>` element. Consumers styling `dialog { ... }` should target the part directly (or its role), and a forwarded ref is now an `HTMLDivElement`; `...props` accept `ComponentProps<'div'>`.
+
+  The dialog window is the initial focus target — focusable in script, out of the tab order — which needs `tabindex="-1"`, and HTML states that [the `tabindex` attribute must not be specified on `dialog` elements](https://html.spec.whatwg.org/multipage/interactive-elements.html#the-dialog-element). The native element would only pay off through `showModal()`, and this contract deliberately keeps modality, dismissal, and focus in the core machine rather than splitting authority with the browser's built-in behavior — so the element brought nothing but a conformance violation. Nothing about the exposed semantics changes: the same role, `aria-modal`, name, description, and focus behavior as before. UA `<dialog>` resets (`position: static`, `border: none`) are no longer needed in consumer styles.
+
 ## 0.2.2
 
 ### Patch Changes
diff --git a/packages/react/dialog/package.json b/packages/react/dialog/package.json
index 2febb6d..48b343e 100644
--- a/packages/react/dialog/package.json
+++ b/packages/react/dialog/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@dunky.dev/react-dialog",
-  "version": "0.2.2",
+  "version": "0.3.0",
   "description": "React binding for @dunky.dev/dialog.",
   "license": "MIT",
   "repository": {