diff --git a/CHANGELOG.md b/CHANGELOG.md index 46059c1..6326922 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,20 @@ All notable changes to this project are documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). +## [0.4.1] - 2026-08-20 + +No code changes. Every emitted file is byte-identical to 0.4.0 except the banner line of +`dist/cereale.min.js`, which carries the version string. This exists because the README +inside the 0.4.0 tarball is the one npmjs.com renders, and it said the package was not on +npm: *"`npm install cereale` does not resolve to this library — the name is unclaimed on +the registry."* True when it was written, nonsense on the package page of the thing it +describes. + +0.4.0 was the first publish, so nothing could have carried the corrected text: the docs +could only be fixed after the registry proved the claim wrong. The install instructions, +the landing page panel, and the "what cereale is not" entry now say `npm install cereale`, +and the README carries an npm version badge. + ## [0.4.0] - 2026-08-05 ### `cereale/min` — one file, no bundler diff --git a/docs/index.html b/docs/index.html index ff19890..3e29892 100644 --- a/docs/index.html +++ b/docs/index.html @@ -410,7 +410,7 @@ footer { border-top: 1px solid var(--border); padding-block: 2.5rem; color: var(
- cereale v0.4.0 + cereale v0.4.1

It is still 0.x

-

0.4.0 is published, and under semver a 0.x minor bump +

0.4.1 is published, and under semver a 0.x minor bump is allowed to break you. Pin the version until 1.0; the changelog says what moved and why.

diff --git a/docs/meta.js b/docs/meta.js index e7ae56a..fae4bca 100644 --- a/docs/meta.js +++ b/docs/meta.js @@ -1,5 +1,5 @@ // Generated by scripts/build-docs.mjs — do not edit. window.CEREALE_META = { - "version": "0.4.0", + "version": "0.4.1", "node": ">=20.0.0" }; diff --git a/package-lock.json b/package-lock.json index 7d3644d..fc191f4 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "cereale", - "version": "0.3.0", + "version": "0.4.1", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "cereale", - "version": "0.3.0", + "version": "0.4.1", "license": "MIT", "devDependencies": { "@babel/standalone": "^8.0.4", diff --git a/package.json b/package.json index 6810472..56e8884 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "cereale", - "version": "0.4.0", + "version": "0.4.1", "description": "Strongly typed JSON mapping and validation for TypeScript classes \u2014 validated domain objects, not validated data. A zero-dependency replacement for class-validator + class-transformer, on TC39 standard decorators.", "type": "module", "main": "./dist/cjs/index.js", diff --git a/scripts/build-docs.mjs b/scripts/build-docs.mjs index 0e75ebd..dc186d4 100644 --- a/scripts/build-docs.mjs +++ b/scripts/build-docs.mjs @@ -49,6 +49,27 @@ await writeFile( `window.CEREALE_META = ${JSON.stringify({ version: pkg.version, node: pkg.engines.node }, null, 2)};\n` ); +// 2b. The same version, stamped into the two spots in index.html that page.js later +// overwrites from meta.js. Those are the no-JavaScript fallbacks: correct in a browser, +// stale in a text reader or a scraper, and hand-bumped until now — they went stale on +// 0.4.0 and again on 0.4.1. Stamping them here means the docs-sync gate catches the +// drift instead of a reviewer. The regexes are asserted, so if the markup is renamed +// the build fails loudly rather than silently stamping nothing. +const indexPath = path.join(docs, 'index.html'); +let index = await readFile(indexPath, 'utf8'); +const stamps = [ + [/()v[\d.]+(<\/span>)/, `$1v${pkg.version}$2`], + [/()[\d.]+(<\/span>)/g, `$1${pkg.version}$2`], +]; +for (const [re, replacement] of stamps) { + if (!re.test(index)) { + console.error(`build-docs: nothing in docs/index.html matched ${re} — the version fallback markup moved.`); + process.exit(1); + } + index = index.replace(re, replacement); +} +await writeFile(indexPath, index); + // 3. The compiler errors the page quotes, produced by actually running the compiler. If a // snippet the page calls a compile error ever compiles, this fails the build. const { byCase, problems } = await collectDiagnostics(root);