2026-08-20 — One release-notes format and a CHANGELOG that describes this package
Documentation only. No source file, configuration file, or exported symbol changed.
The documentation had drifted between several release-note formats. Standardising the shape here surfaced that this
repository's CHANGELOG.md had never been updated after the initial scaffold.
The CHANGELOG described a different package
Both version sections belonged to the library scaffold this repository started from. ## [1.0.0] - 2026-04-19 was
"initial repository scaffold for a Node.js library template", and ## [1.1.0] - 2026-08-05 was the scaffold's own
modernisation — HonKit replacing GitBook, a stale UMD global renamed, and docs/changes-log/2026-apr-19.md renamed for
ISO consistency.
Meanwhile docs/release-notes/1.0.0.md documented the extraction of vendored adapters and docs/release-notes/1.1.0.md
documented analytics.minRequestStatus. Each version section closed with See docs/release-notes/<version>.md
for full release details — a link to a document about something else entirely. Nothing failed, because a
cross-reference that is merely wrong does not break a build.
[1.0.0] and [1.1.0] now describe this package, matching the release notes and dated to match them: 2026-08-06 for
the extraction, 2026-08-08 for the analytics threshold.
The scaffold's entries are kept, not deleted, under a trailing ## Project scaffold history section, demoted a
level so the version numbers no longer collide. The build, @/* mapping, TypeDoc gate, and documentation portal still
come from that scaffold, so the record remains useful without identifying another repository.
Release notes
docs/release-notes/1.0.0.md and 1.1.0.md were free-form prose under a bare # <version> heading. They now open with
# Release Notes and ## Version <x.y.z>, and the prose is sorted into the emoji sections the family uses — 📅 📖
🚀 🔧 ⚠️ 🔐 🧪 📚 🚨 📦 ⬆️ 👥 🙏 — closing with the line pointing at the GitHub repository.
Nothing was cut. The reasoning that made these documents worth reading — why the kernel must stay external, why
lazySettings exists, why the analytics threshold lives in the service rather than the middleware — is all still there,
now under a heading that says which kind of statement it is.
The publishing guide
docs/guides/publishing.md already carried a table of the release-notes sections. It is updated to the full canonical
list, including the sections this repository's own notes use that the table did not name (🧪 Tests,
📚 Documentation), and it now states the file's opening and closing lines rather than leaving them to be inferred from
whichever note was copied.