pro-editor-schema 1.2.6 → 1.3.0

package/README.md

@@ -32,7 +32,7 @@ For local development, `npm run check` is the fastest way to verify everything b
 
 ## Publishing
 
-The package is published to npm as `pro-editor-schema`. Use the `staging` tag for pre-release installs, and the default `latest` tag for production.
+The package is published to npm as `pro-editor-schema`. Use the `beta` tag for pre-release installs, and the default `latest` tag for latest.
 
 ### Prerequisites
 
@@ -50,19 +50,19 @@ npm login
 npm run check
 ```
 
-### Publish to staging
+### Publish to beta
 
 ```bash
-npm publish --tag staging --access public
+npm publish --tag beta --access public
 ```
 
-Install the staging build in a consumer app with:
+Install the beta build in a consumer app with:
 
 ```bash
-npm install pro-editor-schema@staging
+npm install pro-editor-schema@beta
 ```
 
-### Publish to production
+### Publish to latest
 
 Production uses npm’s default `latest` tag:
 
@@ -70,7 +70,7 @@ Production uses npm’s default `latest` tag:
 npm publish --access public
 ```
 
-Install the production build with:
+Install the latest build with:
 
 ```bash
 npm install pro-editor-schema
@@ -82,7 +82,7 @@ npm install pro-editor-schema@latest
 
 - Always run `npm run check` before publishing so typecheck, lint, tests, and build succeed.
 - Each publish needs a new `version` in `package.json`.
-- Staging and production can point at different versions at the same time (for example `1.1.3` on `staging` and `1.1.2` on `latest`).
+- Staging and latest can point at different versions at the same time (for example `1.1.3` on `beta` and `1.1.2` on `latest`).
 - GitHub Actions also publishes to `latest` when you push a `v*` git tag (see `.github/workflows/publish.yml`).
 
 ## CI

package/dist/index.js

@@ -3168,7 +3168,7 @@ var validateHeadingHierarchy = (element) => {
     store: getStore(element),
     title: "Invalid heading hierarchy",
     kind: "forbidden",
-    description: "The nesting of the heading tags is incorrect. Please contact Support.",
+    description: `H${level} cannot follow H${parentLevel} directly. Please check the heading hierarchy.`,
     level: "warning"
   });
   return errors;

package/dist/index.mjs

@@ -3088,7 +3088,7 @@ var validateHeadingHierarchy = (element) => {
     store: getStore(element),
     title: "Invalid heading hierarchy",
     kind: "forbidden",
-    description: "The nesting of the heading tags is incorrect. Please contact Support.",
+    description: `H${level} cannot follow H${parentLevel} directly. Please check the heading hierarchy.`,
     level: "warning"
   });
   return errors;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pro-editor-schema",
-  "version": "1.2.6",
+  "version": "1.3.0",
   "description": "Pro Editor XML schemas",
   "main": "dist/index.js",
   "module": "dist/index.mjs",