@liminis/editor 0.1.0-rc.2 → 0.1.0

package/README.md

@@ -28,16 +28,14 @@ travelled with the code, are recorded in [`docs/provenance.md`](./docs/provenanc
 
 ## Install
 
-> **This package is published as a prerelease.** `0.1.0-rc.1` is on npm under the
-> `next` tag, so `pnpm add @liminis/editor` resolves nothing — ask for the tag:
->
-> ```bash
-> pnpm add @liminis/editor@next
-> ```
->
-> The prerelease exists to prove the registry install path, which nothing had
-> exercised: both consuming applications resolved this package locally. `latest`
-> stays unset until `0.1.0`.
+```bash
+pnpm add @liminis/editor
+```
+
+> **This is `0.x`.** Minor versions may contain breaking changes; patch versions
+> will not. The seven declared subpath exports are the public API — anything
+> reachable by a deeper path is private and may move without notice. Breaking
+> changes are listed in the changelog with a migration note.
 
 React and Lexical are **peer dependencies**, so your app resolves exactly one
 copy of each. Two React copies produce `Invalid hook call`; two Lexical copies
@@ -265,7 +263,7 @@ inert).
 
 ## Consuming it
 
-The registry is now the normal route (`pnpm add @liminis/editor@next`). The
+The registry is the normal route (`pnpm add @liminis/editor`). The
 **packed tarball** below remains the way to consume an unreleased change — a
 local build, or a commit that has not been tagged:
 

package/package.json

@@ -1,9 +1,21 @@
 {
   "name": "@liminis/editor",
-  "version": "0.1.0-rc.2",
+  "version": "0.1.0",
   "//publishing": "Publishing is deliberate, never incidental. `private: true` was this package's guard until verveguy/liminis-editor#39 took the publish decision; it is gone because that decision was taken, not because it was tidied away. The guard is now `prepublishOnly` -> scripts/guard-publish.mjs, which refuses unless LIMINIS_ALLOW_PUBLISH=1 is set explicitly. That variable is set at step scope in .github/workflows/publish.yml and nowhere else, so a release is the only path that publishes. Note that `npm publish --dry-run` does NOT report a private package as blocked (npm 10.8.2), which is why the guard is a script rather than a flag.",
   "license": "MIT",
   "description": "Lexical-based markdown WYSIWYG editor with mdast round-trip and a host-injection seam",
+  "keywords": [
+    "markdown",
+    "markdown-editor",
+    "wysiwyg",
+    "rich-text",
+    "editor",
+    "lexical",
+    "react",
+    "mdast",
+    "round-trip",
+    "annotations"
+  ],
   "//packageManager": "Not cosmetic. This field used to live in the monorepo root manifest and did not travel with the package, so `pnpm/action-setup` had no version to read and CI failed before installing anything. It is also what pins the pnpm that resolves the lockfile.",
   "packageManager": "pnpm@10.33.0",
   "type": "module",