@curly-message/conformance 1.0.0-next.0 → 1.0.0-next.2

package/README.md

@@ -247,7 +247,8 @@ The reference implementation is what the set is checked against before it
 lands, and the set is what the reference is checked against in turn. Where
 the two disagree, the specification decides which is wrong.
 
-`npm run manifest` regenerates `index.json` from the files; the tests fail
+`npm run manifest` regenerates `index.json` from the files, and a version bump
+runs it; the tests fail
 where it is stale, where an `id` repeats, where a file does not validate
 against the schema, or where a `section` names no heading of `SPEC.md`.
 

package/index.json

@@ -1,6 +1,6 @@
 {
   "format": "curly-message-1",
-  "version": "1.0.0-next.0",
+  "version": "1.0.0-next.2",
   "files": [
     {
       "path": "fixtures/comparisons.json",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@curly-message/conformance",
-  "version": "1.0.0-next.0",
+  "version": "1.0.0-next.2",
   "description": "Conformance fixtures and runner for the Curly Message Format.",
   "type": "module",
   "types": "./dist/index.d.ts",
@@ -15,7 +15,7 @@
     "./package.json": "./package.json"
   },
   "bin": {
-    "curly-message-conformance": "./bin/conformance.js"
+    "curly-message-conformance": "bin/conformance.js"
   },
   "engines": {
     "node": ">=22"
@@ -27,6 +27,7 @@
     "test": "vitest run",
     "build": "tsup",
     "prepack": "npm run build",
+    "version": "npm run manifest",
     "lint": "eslint . --max-warnings=0",
     "lint:fix": "eslint --fix .",
     "manifest": "node ./bin/manifest.js",