chore(release): 0.1.1 (#13)

The version and the documents that name it, nothing else. The fix this
release carries went in separately as #12, so this commit stays reviewable
as what it is: five manifests, the changelog entry that was already written
under `[Unreleased]`, and the one README sentence that has a version in it.

`latest` is meant to move to 0.1.1. The public surface did not change —
`pnpm api` reports all five reports unchanged — so a patch is the honest
number.

The README sentence now says `0.1.x` rather than a single version, because
what it claims is true of the line and not of one release: below 1.0.0 the
minor carries the breaking change, so no caret range crosses it. Written
that way it does not go stale on the next patch.

Root and `demo` keep 0.1.0. Neither is published, and the last release left
them alone for the same reason.

Author: htcom-code

CHANGELOG.md

@@ -9,6 +9,10 @@ version lines would multiply into combinations nobody tests.
 
 ## [Unreleased]
 
+Nothing since 0.1.1.
+
+## [0.1.1] — 2026-08-10
+
 ### Fixed
 
 - **A range covering no byte no longer breaks the decoration indexes.** One zero-length
@@ -116,6 +120,7 @@ things a consumer would have met and no test could see.
   zero; the rest is down to 132, with the remainder being platform callbacks and button
   labels where a comment would restate the name.
 
-[Unreleased]: https://github.com/htcom-code/hexcanvas/compare/v0.1.0...main
+[Unreleased]: https://github.com/htcom-code/hexcanvas/compare/v0.1.1...main
+[0.1.1]: https://github.com/htcom-code/hexcanvas/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/htcom-code/hexcanvas/compare/v0.1.0-next.0...v0.1.0
 [0.1.0-next.0]: https://github.com/htcom-code/hexcanvas/releases/tag/v0.1.0-next.0

README.md

@@ -70,8 +70,8 @@ the cursor.*
 npm install @hexcanvas/core @hexcanvas/element   # or pnpm add / yarn add
 ```
 
-> **0.1.0 is a first release, not a settled API.** The version says so: below 1.0.0 the
-> minor is the breaking position, so `^0.1.0` will not carry you across a change of
+> **0.1.x is an early line, not a settled API.** The version says so: below 1.0.0 the
+> minor is the breaking position, so `^0.1.1` will not carry you across a change of
 > shape. The decoration surface changed twice in a single session before this was public.
 > [ROADMAP.md](ROADMAP.md) says which parts are deliberately unfinished.
 

packages/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hexcanvas/core",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Framework-free hex editor core: byte sources, grid geometry, canvas renderer and editing engine.",
   "keywords": [
     "hex",

packages/element/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hexcanvas/element",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "<hexcanvas-editor> custom element: a hex viewer and editor usable from any framework.",
   "keywords": [
     "hex",

packages/react/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hexcanvas/react",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "React binding for HexCanvas: a canvas-rendered hex viewer and editor.",
   "keywords": [
     "hex",

packages/svelte/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hexcanvas/svelte",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Svelte action and mount helper for HexCanvas, over the <hexcanvas-editor> custom element.",
   "keywords": [
     "hex",

packages/vue/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hexcanvas/vue",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Vue binding for HexCanvas, wrapping the <hexcanvas-editor> custom element.",
   "keywords": [
     "hex",