From df1999b5281f21af912b9316458b70383009bcb5 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Sun, 6 Sep 2026 14:09:09 +0000
Subject: [PATCH] Version Packages

---
 .../base-ui-native-button-native-render.md     | 17 -----------------
 packages/nk-dev/CHANGELOG.md                   | 18 ++++++++++++++++++
 packages/nk-dev/package.json                   |  2 +-
 3 files changed, 19 insertions(+), 18 deletions(-)
 delete mode 100644 .changeset/base-ui-native-button-native-render.md

diff --git a/.changeset/base-ui-native-button-native-render.md b/.changeset/base-ui-native-button-native-render.md
deleted file mode 100644
index f28f7d6..0000000
--- a/.changeset/base-ui-native-button-native-render.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-"@ingram-tech/nk-dev": patch
----
-
-`nextkit/base-ui-native-button` now only inspects components that actually
-accept `nativeButton`: Button, PopoverTrigger, Switch and the menu items.
-
-Keying on the `Button` / `Trigger` name suffixes was wrong twice. A
-`*Trigger` builds on `useButton` internally but does not expose the prop, so
-the rule demanded code that does not type-check; and a render target named
-`*Button` is Base UI's own primitive or a wrapper on it, which renders a
-native `<button>`, where `nativeButton={false}` earns the inverse runtime
-warning. A locally defined component that merely shares the name (a
-SidebarMenuButton) took no such prop either.
-
-On one site this took the rule from 81 reports, 55 of them wrong and the rest
-unfixable as suggested, to only the genuine `Button render={<Link />}` cases.
diff --git a/packages/nk-dev/CHANGELOG.md b/packages/nk-dev/CHANGELOG.md
index fb36ccd..30ab608 100644
--- a/packages/nk-dev/CHANGELOG.md
+++ b/packages/nk-dev/CHANGELOG.md
@@ -1,5 +1,23 @@
 # @ingram-tech/nk-dev
 
+## 0.16.1
+
+### Patch Changes
+
+- 54eec07: `nextkit/base-ui-native-button` now only inspects components that actually
+  accept `nativeButton`: Button, PopoverTrigger, Switch and the menu items.
+  
+  Keying on the `Button` / `Trigger` name suffixes was wrong twice. A
+  `*Trigger` builds on `useButton` internally but does not expose the prop, so
+  the rule demanded code that does not type-check; and a render target named
+  `*Button` is Base UI's own primitive or a wrapper on it, which renders a
+  native `<button>`, where `nativeButton={false}` earns the inverse runtime
+  warning. A locally defined component that merely shares the name (a
+  SidebarMenuButton) took no such prop either.
+  
+  On one site this took the rule from 81 reports, 55 of them wrong and the rest
+  unfixable as suggested, to only the genuine `Button render={<Link />}` cases.
+
 ## 0.16.0
 
 ### Minor Changes
diff --git a/packages/nk-dev/package.json b/packages/nk-dev/package.json
index 7b4da91..d1202ee 100644
--- a/packages/nk-dev/package.json
+++ b/packages/nk-dev/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "@ingram-tech/nk-dev",
-	"version": "0.16.0",
+	"version": "0.16.1",
 	"description": "The nextkit dev toolchain in one package: the `nk` CLI plus shared oxlint/oxfmt, TypeScript, and Vitest config, the format-on-commit hook, and the AI agent guide. `nk init` scaffolds a site to use it.",
 	"license": "MIT",
 	"type": "module",