From 8c575559a37dd09f325b7700c3e66b822b56b7c5 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Wed, 26 Aug 2026 23:13:53 +0000
Subject: [PATCH] chore(release): bump versions

---
 .../rjsf-6-peer-range-and-theme-prop.md       | 38 ------------------
 packages/forms-rjsf/CHANGELOG.md              | 40 +++++++++++++++++++
 packages/forms-rjsf/package.json              |  2 +-
 3 files changed, 41 insertions(+), 39 deletions(-)
 delete mode 100644 .changeset/rjsf-6-peer-range-and-theme-prop.md
 create mode 100644 packages/forms-rjsf/CHANGELOG.md

diff --git a/.changeset/rjsf-6-peer-range-and-theme-prop.md b/.changeset/rjsf-6-peer-range-and-theme-prop.md
deleted file mode 100644
index 2640a6c..0000000
--- a/.changeset/rjsf-6-peer-range-and-theme-prop.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-'acture-forms-rjsf': minor
----
-
-Accept `@rjsf` 6.x, and make the RJSF theme injectable.
-
-The `@rjsf/core` / `@rjsf/utils` / `@rjsf/validator-ajv8` peer ranges move from
-`^5.20.0` to `^5.20.0 || ^6.0.0`. `@rjsf/shadcn` is published on the 6.x line
-only, so the old range made the shadcn theme — the one every frontend in this
-ecosystem wants — impossible to install alongside this adapter. The failure was
-an npm peer conflict at install time, i.e. before a line of form code got
-written. No adapter code was needed to span the two majors: `@rjsf/core`'s
-default export and `FormProps`, `@rjsf/validator-ajv8`'s default export, and the
-`schema` / `formData` / `validator` / `liveValidate` / `onSubmit` / children
-props are shape-identical on both.
-
-`<RjsfForm />` gains an optional **`form`** prop taking any RJSF theme's
-`<Form />` (`ComponentType<FormProps>` — the type every theme's default export
-already has), defaulting to the unstyled `@rjsf/core` form:
-
-```tsx
-import ShadcnForm from '@rjsf/shadcn';
-<RjsfForm form={ShadcnForm} command={cmd} onSubmit={run} onCancel={close} />;
-```
-
-Before this, the README told you to "pass your own `Form` from the themed
-package" and there was no prop that accepted one. acture still bundles no UI kit
-(hard-don't #8) — the theme is the host's, injected.
-
-Both halves of the widened range are checked on every PR: the main CI job
-installs and tests 6.x, and a second job installs its own plain 5.x tree and
-typechecks + tests the adapter against it.
-
-The `form` value must be referentially stable (bind a theme at module level) —
-React reconciles by element type, so an inline `withTheme(...)` remounts the
-form and discards in-progress input. Documented on the prop and in the README.
-
-Also exported: the `RjsfFormComponent` type.
diff --git a/packages/forms-rjsf/CHANGELOG.md b/packages/forms-rjsf/CHANGELOG.md
new file mode 100644
index 0000000..a4f3bb1
--- /dev/null
+++ b/packages/forms-rjsf/CHANGELOG.md
@@ -0,0 +1,40 @@
+# acture-forms-rjsf
+
+## 1.1.0
+
+### Minor Changes
+
+- ea386c7: Accept `@rjsf` 6.x, and make the RJSF theme injectable.
+
+  The `@rjsf/core` / `@rjsf/utils` / `@rjsf/validator-ajv8` peer ranges move from
+  `^5.20.0` to `^5.20.0 || ^6.0.0`. `@rjsf/shadcn` is published on the 6.x line
+  only, so the old range made the shadcn theme — the one every frontend in this
+  ecosystem wants — impossible to install alongside this adapter. The failure was
+  an npm peer conflict at install time, i.e. before a line of form code got
+  written. No adapter code was needed to span the two majors: `@rjsf/core`'s
+  default export and `FormProps`, `@rjsf/validator-ajv8`'s default export, and the
+  `schema` / `formData` / `validator` / `liveValidate` / `onSubmit` / children
+  props are shape-identical on both.
+
+  `<RjsfForm />` gains an optional **`form`** prop taking any RJSF theme's
+  `<Form />` (`ComponentType<FormProps>` — the type every theme's default export
+  already has), defaulting to the unstyled `@rjsf/core` form:
+
+  ```tsx
+  import ShadcnForm from "@rjsf/shadcn";
+  <RjsfForm form={ShadcnForm} command={cmd} onSubmit={run} onCancel={close} />;
+  ```
+
+  Before this, the README told you to "pass your own `Form` from the themed
+  package" and there was no prop that accepted one. acture still bundles no UI kit
+  (hard-don't #8) — the theme is the host's, injected.
+
+  Both halves of the widened range are checked on every PR: the main CI job
+  installs and tests 6.x, and a second job installs its own plain 5.x tree and
+  typechecks + tests the adapter against it.
+
+  The `form` value must be referentially stable (bind a theme at module level) —
+  React reconciles by element type, so an inline `withTheme(...)` remounts the
+  form and discards in-progress input. Documented on the prop and in the README.
+
+  Also exported: the `RjsfFormComponent` type.
diff --git a/packages/forms-rjsf/package.json b/packages/forms-rjsf/package.json
index 8474774..af5795f 100644
--- a/packages/forms-rjsf/package.json
+++ b/packages/forms-rjsf/package.json
@@ -1,6 +1,6 @@
 {
   "name": "acture-forms-rjsf",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "JSON-Schema-native form adapter for acture-palette-react built on react-jsonschema-form (@rjsf/core 5.x or 6.x), with a pluggable theme.",
   "license": "Apache-2.0",
   "author": "Thor Whalen",