diff --git a/.tegami/2026-07-28-9c4e2b.md b/.tegami/2026-07-28-9c4e2b.md
deleted file mode 100644
index dfb1389a..00000000
--- a/.tegami/2026-07-28-9c4e2b.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-packages:
-  "npm:@reactunity/renderer": patch
----
-
-### Fix gradients rendering too dark in gamma colour space
-
-Every gradient — `linear-gradient`, `radial-gradient`, `conic-gradient` and their repeating forms — had its colours converted to linear space regardless of the project's colour space. A gamma-space project never converts them back, so the whole ramp came out darkened by a 2.2 exponent: CSS `green` painted as `rgb(0,55,0)` rather than `rgb(0,128,0)`, and `linear-gradient(red, blue)` crossed at `rgb(54,0,55)` rather than `rgb(127,0,128)`. Saturated endpoints survived while everything between them sank toward black.
-
-The ramp is stored in a texture flagged linear and its contents have to agree with that flag, so the conversion is right in a linear-space project and stays. It now follows `QualitySettings.activeColorSpace` instead of applying unconditionally. Gamma-space projects again match what a browser paints for the same CSS declaration, to the byte.
-
-Introduced in 0.23.0. Projects on Linear colour space were never affected, and need no changes.
diff --git a/.tegami/2026-07-29-b71c4e.md b/.tegami/2026-07-29-b71c4e.md
deleted file mode 100644
index 16a2988f..00000000
--- a/.tegami/2026-07-29-b71c4e.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-packages:
-  "npm:@reactunity/renderer": patch
----
-
-### Fix non-solid border styles rendering as solid until the next style update
-
-`inset`, `outset`, `groove`, `ridge`, `dotted`, `dashed` and `double` borders came out flat solid on an element's first render. Any later style update — a hot reload, a state change, anything that re-ran the style pass — painted them correctly, so in the Editor they appeared to work while a build, where no such update ever arrives, showed solid borders forever.
-
-The style is encoded as UVs into a lookup texture that the border graphic samples. That texture was bound from the `Rounding` setter alone, and the graphic is also created from the layout pass, which never assigns rounding: styles run before layout, so on the first pass Yoga has no border widths yet and no border graphic exists to receive the rounding, and by the time the layout pass creates one the style pass is over. With no texture bound, Unity substitutes a white one and every style samples as solid.
-
-The texture is now resolved on each material rebuild instead of being cached on assignment, so it is correct however the graphic came to exist.
-
-Borders with a `border-radius` still ignore `border-style` and paint solid — a separate, pre-existing limitation of the rounded mesh path.
diff --git a/.tegami/2026-07-29-e35a90.md b/.tegami/2026-07-29-e35a90.md
deleted file mode 100644
index c970dbb2..00000000
--- a/.tegami/2026-07-29-e35a90.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-packages:
-  "npm:@reactunity/renderer": patch
----
-
-### Support border-style and outline-style on rounded corners
-
-`border-radius` used to drop `border-style` entirely: the rounded mesh path sampled no style at all, so every style painted as flat solid, and `none` painted a solid border rather than nothing. Browsers render all of them with rounded corners, so a declaration that worked on a square element silently lost its style once a radius was added. `outline-style` was dropped the same way. All seven styles now render along the curve.
-
-`groove`, `ridge`, `inset`, `outset` and `double` are ramps across the border width, and the rounded path already emitted an inner and an outer vertex ring stitched 1:1 into a quad strip. Feeding the style band's inner edge to the inner ring and its outer edge to the outer ring makes the strip interpolate the ramp, using the same bands and the same per-side inversion as the square path.
-
-`dotted` and `dashed` repeat *along* the edge instead, which one continuous ring cannot express. When a side asks for one, the rings are emitted as vertices only and each side is drawn as its own strip, walked out by arc length along the border's centreline so a dash keeps its length through a corner. The dash and dot counts are fitted to a whole number per side, so a side begins and ends with half a gap rather than a clipped dash at the mitre. Sides can mix freely - a dashed top against solid sides keeps a clean mitre, since each corner arc doubles its vertex at 45 degrees and the per-side split lands exactly on that pair.
diff --git a/.tegami/2026-07-30-6d2b81.md b/.tegami/2026-07-30-6d2b81.md
deleted file mode 100644
index e8784f30..00000000
--- a/.tegami/2026-07-30-6d2b81.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-packages:
-  "upm:com.reactunity.jint": minor
-  "upm:com.reactunity.core": minor
----
-
-### Update Jint to 4.15.3
-
-`com.reactunity.jint` carried a 4.0.0-beta build; it now ships Jint 4.15.3 and Acornima 1.6.2. `System.Collections.Immutable` and `System.Reflection.Metadata` are gone with it — 4.15 no longer depends on either — while `Jint.dll` grew from 0.9 MB to 2.5 MB, most of it the Intl and time-zone data Jint now bundles.
-
-Two behaviours changed under us and are handled in `JintEngine`:
-
-**`import.meta.url` is no longer filled in by Jint.** It used to report the specifier a module was added under; 4.15 leaves `import.meta` to the host, which is what the spec asks for. A `Jint.Runtime.Host` supplies `url` from the module's location again, so the Vite HMR client keeps reading its own address off it. The cache-busting query on the specifier is still needed — re-adding a specifier is still a no-op, so a hot update would otherwise re-run the first version of the module.
-
-**Tasks are now promises.** A `Task` handed to script code was an ordinary CLR wrapper, so `await` on one did nothing useful and the test covering it was skipped for Jint. It is now converted through a wrap handler, matching what QuickJS and ClearScript already did. Jint 4.15 has its own `ExperimentalFeature.TaskInterop` for this, but it rejects with the `AggregateException` wrapping the failure; the handler here rejects with the inner exception, so a `catch` sees the same error on all three engines.
-
-Two pieces of glue went with the update. The `Esprima.NET` fallback in `TryExecute` and the `REACT_JINT_ACORNIMA` version define that selected it are gone — Jint has parsed with Acornima since 4.0, and `Esprima.dll` has not shipped since 0.20.0. `ObjectWrapper` also reads `Array.prototype` methods off a CLR list now, so `reduce`, `map` and friends work on a `List<T>` without spreading it first; the mutating half (`splice`, assigning `length`) still throws, because Jint wraps the list read-only on Unity's runtime, and that test stays skipped for Jint alone.
diff --git a/.tegami/2026-07-30-a1c9f4.md b/.tegami/2026-07-30-a1c9f4.md
deleted file mode 100644
index 25095140..00000000
--- a/.tegami/2026-07-30-a1c9f4.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-packages:
-  "upm:com.reactunity.core": minor
-  "upm:com.reactunity.quickjs": minor
----
-
-### Run a Vite dev server, entry document and HMR patches included
-
-Pointing `DevServer` at a Vite server root now works on every engine.
-
-A dev server answers its root with an HTML entry document rather than JavaScript — Vite's is a bare `<script type="module" crossorigin src="/assets/index.js">` — so the engine was handed markup. That content is now detected and its script tags are run. Only the scripts: the rest of an index.html describes a browser page. It does not go through `HtmlParser`, which is strict XML and rejects ordinary HTML5 (Vite's valueless `crossorigin` alone was enough to fail the load); an explicit `ScriptSourceLanguage.Html` source still parses as before.
-
-The check prefers a declared type over a guess: the response `Content-Type`, then the extension, and only sniffing the first character when neither exists — which is the usual case for a `TextAsset` or an extensionless resource. Content-Type deliberately outranks the extension, because Vite's SPA fallback answers `/index.js` with the entry document.
-
-**Jint and QuickJS now execute real ES modules.** Both were accepting `JavascriptDocumentType.Module` and parsing as a script regardless, which is why `import.meta` and `export` failed on them. Jint 4 goes through `Engine.Modules`, QuickJS through a module eval that was already in the binding but never reachable. QuickJS also only filled in `import.meta` for modules that arrived via its loader, leaving `import.meta.url` undefined on a module evaluated straight from source; it is now compiled first so the url can be set before the body runs. Module-shaped bundler output is therefore run as a module rather than rewritten, and nothing rewrites module syntax any more.
-
-Executing a module is not the same as resolving one, so those are separate capabilities. Jint and QuickJS resolve specifiers only through a local file system, and Vite's HMR client applies every patch with `import(url)` against the dev server. Dynamic imports on those two engines are pointed at a host loader that fetches the chunk and executes it; ClearScript, which has an HTTP document loader already, is left alone.
-
-`build.rollupOptions.output.format: 'iife'` must be scoped to `command === 'build'`. `experimental.bundledDev` bundles the dev server output with the same options, and under iife rolldown rewrites `import.meta` to `{}`, which makes Vite's HMR client throw on `new URL(import.meta.url)` before it opens its socket — the connection dies silently at `[vite] connecting...`, in browsers too. The Kitchen Sink config shows the shape.
diff --git a/.tegami/2026-07-30-c73d51.md b/.tegami/2026-07-30-c73d51.md
deleted file mode 100644
index ac1c2245..00000000
--- a/.tegami/2026-07-30-c73d51.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-packages:
-  "npm:@reactunity/renderer": patch
----
-
-### Fix React Fast Refresh never repainting a hot-updated component
-
-An edit to a component was fetched, applied and acknowledged by the dev server, and then nothing on screen changed. Both dev servers were affected — webpack and Vite alike — so any hot reload that was not a full page reload silently did nothing.
-
-`render` registered the renderer with the devtools hook *after* committing the tree. React Refresh learns which roots it may refresh from the hook's `onCommitFiberRoot`, and only calls `scheduleRefresh` for roots it has seen mount — so a renderer that registers after its first commit is invisible to it forever. The initial mount was the commit being missed, which meant the app's only root was never a refresh candidate.
-
-`injectIntoDevTools` now runs before the first commit, and once per reconciler rather than on every `render` call — repeated injection was registering the same renderer under a new id each time.
diff --git a/.tegami/publish-lock.yaml b/.tegami/publish-lock.yaml
index db9a1285..4ce6e4d9 100644
--- a/.tegami/publish-lock.yaml
+++ b/.tegami/publish-lock.yaml
@@ -1,6 +1,15 @@
 core:changelogs:
-  - content: "---\npackages:\n  npm:@reactunity/scripts:\n    type: minor\n---\n\n### Serve the web previewer without installing it\n\nThe dev server's previewer now works out of the box. Visiting the dev server address in a browser opens a Unity WebGL player running your UI, with no extra package to install.\n\nPreviously this required the optional `@reactunity/previewer` dependency, which shipped a ~107 MB Unity build in its npm tarball — a cost every install paid for a page many projects never opened. The build is now hosted on `reactunity.github.io` and fetched on first load, then cached by the browser. `@reactunity/previewer` is no longer used and has been dropped from `peerDependencies`; you can remove it from your project.\n\nBecause the build is fetched rather than bundled, the first load needs network access. To preview offline — or to preview your own Unity scene — put a previewer build in a `previewer` folder in your project so that `previewer/index.html` exists. The dev server serves that in preference to the built-in previewer, and your project's own `public` folder takes precedence over both.\n\nThe dev server also serves `/info.html`, explaining how to point Unity's `DevServer` property at it. That guidance used to be the page shown at `/`.\n\n### Fix the `previewer` folder override being ignored\n\nA custom previewer placed in a `previewer` folder was never actually served. The dev server read `paths.appPreviewer`, but that key was only defined when developing `react-unity-scripts` in its own repository — in a published install the path resolved to `undefined`, so the documented override silently did nothing.\n"
-    filename: 2026-07-28-a7f3c1.md
+  - content: "---\npackages:\n  npm:@reactunity/renderer:\n    type: patch\n---\n\n### Fix gradients rendering too dark in gamma colour space\n\nEvery gradient — `linear-gradient`, `radial-gradient`, `conic-gradient` and their repeating forms — had its colours converted to linear space regardless of the project's colour space. A gamma-space project never converts them back, so the whole ramp came out darkened by a 2.2 exponent: CSS `green` painted as `rgb(0,55,0)` rather than `rgb(0,128,0)`, and `linear-gradient(red, blue)` crossed at `rgb(54,0,55)` rather than `rgb(127,0,128)`. Saturated endpoints survived while everything between them sank toward black.\n\nThe ramp is stored in a texture flagged linear and its contents have to agree with that flag, so the conversion is right in a linear-space project and stays. It now follows `QualitySettings.activeColorSpace` instead of applying unconditionally. Gamma-space projects again match what a browser paints for the same CSS declaration, to the byte.\n\nIntroduced in 0.23.0. Projects on Linear colour space were never affected, and need no changes.\n"
+    filename: 2026-07-28-9c4e2b.md
+    v: 0.0.0
+  - content: "---\npackages:\n  npm:@reactunity/renderer:\n    type: patch\n---\n\n### Fix non-solid border styles rendering as solid until the next style update\n\n`inset`, `outset`, `groove`, `ridge`, `dotted`, `dashed` and `double` borders came out flat solid on an element's first render. Any later style update — a hot reload, a state change, anything that re-ran the style pass — painted them correctly, so in the Editor they appeared to work while a build, where no such update ever arrives, showed solid borders forever.\n\nThe style is encoded as UVs into a lookup texture that the border graphic samples. That texture was bound from the `Rounding` setter alone, and the graphic is also created from the layout pass, which never assigns rounding: styles run before layout, so on the first pass Yoga has no border widths yet and no border graphic exists to receive the rounding, and by the time the layout pass creates one the style pass is over. With no texture bound, Unity substitutes a white one and every style samples as solid.\n\nThe texture is now resolved on each material rebuild instead of being cached on assignment, so it is correct however the graphic came to exist.\n\nBorders with a `border-radius` still ignore `border-style` and paint solid — a separate, pre-existing limitation of the rounded mesh path.\n"
+    filename: 2026-07-29-b71c4e.md
+    v: 0.0.0
+  - content: "---\npackages:\n  npm:@reactunity/renderer:\n    type: patch\n---\n\n### Support border-style and outline-style on rounded corners\n\n`border-radius` used to drop `border-style` entirely: the rounded mesh path sampled no style at all, so every style painted as flat solid, and `none` painted a solid border rather than nothing. Browsers render all of them with rounded corners, so a declaration that worked on a square element silently lost its style once a radius was added. `outline-style` was dropped the same way. All seven styles now render along the curve.\n\n`groove`, `ridge`, `inset`, `outset` and `double` are ramps across the border width, and the rounded path already emitted an inner and an outer vertex ring stitched 1:1 into a quad strip. Feeding the style band's inner edge to the inner ring and its outer edge to the outer ring makes the strip interpolate the ramp, using the same bands and the same per-side inversion as the square path.\n\n`dotted` and `dashed` repeat *along* the edge instead, which one continuous ring cannot express. When a side asks for one, the rings are emitted as vertices only and each side is drawn as its own strip, walked out by arc length along the border's centreline so a dash keeps its length through a corner. The dash and dot counts are fitted to a whole number per side, so a side begins and ends with half a gap rather than a clipped dash at the mitre. Sides can mix freely - a dashed top against solid sides keeps a clean mitre, since each corner arc doubles its vertex at 45 degrees and the per-side split lands exactly on that pair.\n"
+    filename: 2026-07-29-e35a90.md
+    v: 0.0.0
+  - content: "---\npackages:\n  npm:@reactunity/renderer:\n    type: patch\n---\n\n### Fix React Fast Refresh never repainting a hot-updated component\n\nAn edit to a component was fetched, applied and acknowledged by the dev server, and then nothing on screen changed. Both dev servers were affected — webpack and Vite alike — so any hot reload that was not a full page reload silently did nothing.\n\n`render` registered the renderer with the devtools hook *after* committing the tree. React Refresh learns which roots it may refresh from the hook's `onCommitFiberRoot`, and only calls `scheduleRefresh` for roots it has seen mount — so a renderer that registers after its first commit is invisible to it forever. The initial mount was the commit being missed, which meant the app's only root was never a refresh candidate.\n\n`injectIntoDevTools` now runs before the first commit, and once per reconciler rather than on every `render` call — repeated injection was registering the same renderer under a new id each time.\n"
+    filename: 2026-07-30-c73d51.md
     v: 0.0.0
 core:packages:
   - id: npm:@reactunity/monorepo
@@ -9,11 +18,14 @@ core:packages:
     updated: true
   - id: npm:@reactunity/material
     updated: true
-  - id: npm:@reactunity/renderer
-    updated: true
   - changelogIds:
-      - 2026-07-28-a7f3c1.md
-    id: npm:@reactunity/scripts
+      - 2026-07-28-9c4e2b.md
+      - 2026-07-29-b71c4e.md
+      - 2026-07-29-e35a90.md
+      - 2026-07-30-c73d51.md
+    id: npm:@reactunity/renderer
+    updated: true
+  - id: npm:@reactunity/scripts
     updated: true
 npm:packages:
   - id: npm:@reactunity/monorepo
diff --git a/packages/create/package.json b/packages/create/package.json
index 2e2e643f..18fc06b4 100644
--- a/packages/create/package.json
+++ b/packages/create/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@reactunity/create",
-  "version": "0.23.0",
+  "version": "0.23.1",
   "description": "Scaffold a ReactUnity app using npm init",
   "license": "MIT",
   "//type": "ESM, as of the chalk 6 / commander 15 upgrade: both dropped CommonJS. index.ts is emitted next to itself as ESM, so `bin` keeps pointing at index.js.",
diff --git a/packages/material/package.json b/packages/material/package.json
index 0bccadee..2e247b5f 100644
--- a/packages/material/package.json
+++ b/packages/material/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@reactunity/material",
-  "version": "0.23.0",
+  "version": "0.23.1",
   "description": "Material Design components and utilities for React Unity",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
diff --git a/packages/renderer/CHANGELOG.md b/packages/renderer/CHANGELOG.md
new file mode 100644
index 00000000..f05e2526
--- /dev/null
+++ b/packages/renderer/CHANGELOG.md
@@ -0,0 +1,35 @@
+## @reactunity/renderer@0.23.1
+
+### Fix gradients rendering too dark in gamma colour space
+
+Every gradient — `linear-gradient`, `radial-gradient`, `conic-gradient` and their repeating forms — had its colours converted to linear space regardless of the project's colour space. A gamma-space project never converts them back, so the whole ramp came out darkened by a 2.2 exponent: CSS `green` painted as `rgb(0,55,0)` rather than `rgb(0,128,0)`, and `linear-gradient(red, blue)` crossed at `rgb(54,0,55)` rather than `rgb(127,0,128)`. Saturated endpoints survived while everything between them sank toward black.
+
+The ramp is stored in a texture flagged linear and its contents have to agree with that flag, so the conversion is right in a linear-space project and stays. It now follows `QualitySettings.activeColorSpace` instead of applying unconditionally. Gamma-space projects again match what a browser paints for the same CSS declaration, to the byte.
+
+Introduced in 0.23.0. Projects on Linear colour space were never affected, and need no changes.
+
+### Fix non-solid border styles rendering as solid until the next style update
+
+`inset`, `outset`, `groove`, `ridge`, `dotted`, `dashed` and `double` borders came out flat solid on an element's first render. Any later style update — a hot reload, a state change, anything that re-ran the style pass — painted them correctly, so in the Editor they appeared to work while a build, where no such update ever arrives, showed solid borders forever.
+
+The style is encoded as UVs into a lookup texture that the border graphic samples. That texture was bound from the `Rounding` setter alone, and the graphic is also created from the layout pass, which never assigns rounding: styles run before layout, so on the first pass Yoga has no border widths yet and no border graphic exists to receive the rounding, and by the time the layout pass creates one the style pass is over. With no texture bound, Unity substitutes a white one and every style samples as solid.
+
+The texture is now resolved on each material rebuild instead of being cached on assignment, so it is correct however the graphic came to exist.
+
+Borders with a `border-radius` still ignore `border-style` and paint solid — a separate, pre-existing limitation of the rounded mesh path.
+
+### Support border-style and outline-style on rounded corners
+
+`border-radius` used to drop `border-style` entirely: the rounded mesh path sampled no style at all, so every style painted as flat solid, and `none` painted a solid border rather than nothing. Browsers render all of them with rounded corners, so a declaration that worked on a square element silently lost its style once a radius was added. `outline-style` was dropped the same way. All seven styles now render along the curve.
+
+`groove`, `ridge`, `inset`, `outset` and `double` are ramps across the border width, and the rounded path already emitted an inner and an outer vertex ring stitched 1:1 into a quad strip. Feeding the style band's inner edge to the inner ring and its outer edge to the outer ring makes the strip interpolate the ramp, using the same bands and the same per-side inversion as the square path.
+
+`dotted` and `dashed` repeat *along* the edge instead, which one continuous ring cannot express. When a side asks for one, the rings are emitted as vertices only and each side is drawn as its own strip, walked out by arc length along the border's centreline so a dash keeps its length through a corner. The dash and dot counts are fitted to a whole number per side, so a side begins and ends with half a gap rather than a clipped dash at the mitre. Sides can mix freely - a dashed top against solid sides keeps a clean mitre, since each corner arc doubles its vertex at 45 degrees and the per-side split lands exactly on that pair.
+
+### Fix React Fast Refresh never repainting a hot-updated component
+
+An edit to a component was fetched, applied and acknowledged by the dev server, and then nothing on screen changed. Both dev servers were affected — webpack and Vite alike — so any hot reload that was not a full page reload silently did nothing.
+
+`render` registered the renderer with the devtools hook *after* committing the tree. React Refresh learns which roots it may refresh from the hook's `onCommitFiberRoot`, and only calls `scheduleRefresh` for roots it has seen mount — so a renderer that registers after its first commit is invisible to it forever. The initial mount was the commit being missed, which meant the app's only root was never a refresh candidate.
+
+`injectIntoDevTools` now runs before the first commit, and once per reconciler rather than on every `render` call — repeated injection was registering the same renderer under a new id each time.
diff --git a/packages/renderer/package.json b/packages/renderer/package.json
index 28e578ce..05fb88f1 100644
--- a/packages/renderer/package.json
+++ b/packages/renderer/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@reactunity/renderer",
-  "version": "0.23.0",
+  "version": "0.23.1",
   "description": "React renderer for Unity3D",
   "types": "dist/index.d.ts",
   "typings": "dist/index.d.ts",
diff --git a/packages/scripts/package.json b/packages/scripts/package.json
index e4504690..27ee1ead 100644
--- a/packages/scripts/package.json
+++ b/packages/scripts/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@reactunity/scripts",
-  "version": "0.23.0",
+  "version": "0.23.1",
   "description": "Configuration and scripts for React Unity.",
   "repository": {
     "type": "git",
diff --git a/unity/clearscript/package.json b/unity/clearscript/package.json
index cae3b38a..7b5c90ce 100644
--- a/unity/clearscript/package.json
+++ b/unity/clearscript/package.json
@@ -6,7 +6,7 @@
     "url": "https://github.com/KurtGokhan"
   },
   "displayName": "React Unity ClearScript",
-  "version": "0.23.0",
+  "version": "0.23.1",
   "unity": "2019.4",
   "description": "ClearScript (V8) Plugin for ReactUnity",
   "keywords": ["ReactUnity", "ClearScript", "V8"],
diff --git a/unity/core/package.json b/unity/core/package.json
index af49caf2..dbae458a 100644
--- a/unity/core/package.json
+++ b/unity/core/package.json
@@ -6,7 +6,7 @@
     "url": "https://github.com/KurtGokhan"
   },
   "displayName": "React Unity",
-  "version": "0.23.0",
+  "version": "0.23.1",
   "unity": "2021.3",
   "description": "React renderer for Unity",
   "keywords": ["React", "Framework", "UI", "UGUI", "UIToolkit"],
diff --git a/unity/jint/package.json b/unity/jint/package.json
index 2690bade..95905c89 100644
--- a/unity/jint/package.json
+++ b/unity/jint/package.json
@@ -6,7 +6,7 @@
     "url": "https://github.com/KurtGokhan"
   },
   "displayName": "React Unity Jint",
-  "version": "0.23.0",
+  "version": "0.23.1",
   "unity": "2019.4",
   "description": "Jint Plugin for ReactUnity",
   "keywords": ["ReactUnity", "Jint"],
diff --git a/unity/quickjs/package.json b/unity/quickjs/package.json
index 139e8393..63e51ba3 100644
--- a/unity/quickjs/package.json
+++ b/unity/quickjs/package.json
@@ -6,7 +6,7 @@
     "url": "https://github.com/KurtGokhan"
   },
   "displayName": "React Unity QuickJS",
-  "version": "0.23.0",
+  "version": "0.23.1",
   "unity": "2019.4",
   "description": "QuickJS Plugin for ReactUnity",
   "keywords": ["ReactUnity", "QuickJS"],