From 62e1b30549b89d6799a5510cf175568a6066708d Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Thu, 10 Sep 2026 14:37:42 +0000
Subject: [PATCH] chore(release): update version

---
 .changeset/tabbed-posts-preview-category-fix.md | 5 -----
 packages/dvz-ui/CHANGELOG.md                    | 6 ++++++
 packages/dvz-ui/package.json                    | 2 +-
 3 files changed, 7 insertions(+), 6 deletions(-)
 delete mode 100644 .changeset/tabbed-posts-preview-category-fix.md

diff --git a/.changeset/tabbed-posts-preview-category-fix.md b/.changeset/tabbed-posts-preview-category-fix.md
deleted file mode 100644
index 0daff65b..00000000
--- a/.changeset/tabbed-posts-preview-category-fix.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@devgateway/dvz-ui-react": patch
----
-
-Fix TCDICORE-601: the Gutenberg block editor's live preview for Tabbed Posts (and other blocks with array attributes such as `categories`) sent array attribute values to the preview iframe as JSON-stringified arrays (e.g. `"[5,7]"`), while the published front end joins them as comma-separated strings (`"5,7"`). The mismatch produced malformed REST query parameters (`&category=[5,7]`) that WordPress could not parse, so the live preview showed incorrectly-filtered posts even though the published page rendered correctly. Array attributes are now comma-joined in `PreviewComponent.tsx` to match the front-end save format; non-array object attributes are unaffected.
diff --git a/packages/dvz-ui/CHANGELOG.md b/packages/dvz-ui/CHANGELOG.md
index b4ba7331..1cfd1d9f 100644
--- a/packages/dvz-ui/CHANGELOG.md
+++ b/packages/dvz-ui/CHANGELOG.md
@@ -1,5 +1,11 @@
 # @devgateway/dvz-ui-react
 
+## 1.9.14
+
+### Patch Changes
+
+- [#296](https://github.com/devgateway/data-viz-ui/pull/296) [`e3149c6`](https://github.com/devgateway/data-viz-ui/commit/e3149c6812a4bd426e8010997e543f412145d0f2) Thanks [@claude](https://github.com/apps/claude)! - Fix TCDICORE-601: the Gutenberg block editor's live preview for Tabbed Posts (and other blocks with array attributes such as `categories`) sent array attribute values to the preview iframe as JSON-stringified arrays (e.g. `"[5,7]"`), while the published front end joins them as comma-separated strings (`"5,7"`). The mismatch produced malformed REST query parameters (`&category=[5,7]`) that WordPress could not parse, so the live preview showed incorrectly-filtered posts even though the published page rendered correctly. Array attributes are now comma-joined in `PreviewComponent.tsx` to match the front-end save format; non-array object attributes are unaffected.
+
 ## 1.9.13
 
 ### Patch Changes
diff --git a/packages/dvz-ui/package.json b/packages/dvz-ui/package.json
index bb760704..e36bbb04 100644
--- a/packages/dvz-ui/package.json
+++ b/packages/dvz-ui/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@devgateway/dvz-ui-react",
-  "version": "1.9.13",
+  "version": "1.9.14",
   "main": "dist/cjs/index.js",
   "module": "dist/esm/index.js",
   "types": "dist/types/index.d.ts",