Changelog

Changes and upgrade notes by version

Changes by version. Unreleased lists changes that are not published to npm yet. Check the installed version with pnpm exec for-humanity --version. Before updating, read the Breaking change and Upgrade notes of the target version. In 0.x, a minor update may also require changes to documents or configuration.

pnpm add -D --save-exact for-humanity@latest

Package files for each version are available from GitHub Releases.

0.33.0 — 2026-11-10

Upgrade: Class names in the generated HTML dropped the wg_, pg_ and ui_ prefixes, so wg_article__root is now article__root and pg_status__root is statusPage__root. The inline custom properties --wg-article-* and --wg-cursor-face-* lost the wg- part too. Styles or scripts in your documents that selected those names need the new ones. Otherwise existing projects remain compatible unless a folder is named dist-private. That name is now reserved for the private site output, like dist. A document folder with that name is skipped, and a content path with that name is rejected. Rename the folder to keep using it.

0.32.0 — 2026-11-06

Upgrade: Links in the body now open in a new tab by default. Set linkTarget: "same-tab" in for-humanity.config.ts to keep the previous behavior. Rebuild and redeploy to apply the Details fix.

0.31.4 — 2026-11-03

Upgrade: Existing projects remain compatible. Rebuild and redeploy to get the default favicon back.

0.31.3 — 2026-11-03

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the Mermaid fix. A project that pinned a local patch for this (patches/for-humanity@0.31.1.patch) can drop it. 0.31.2 was tagged but its release failed on lint before publishing, so this is the first version with the fix.

0.31.1 — 2026-11-03

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the marked image size fix.

0.31.0 — 2026-11-03

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the Details status position, marked images, table row targets and one-line identifier links. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.30.0 — 2026-11-02

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the figure box, the lighter list bullets and the Details changes. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.29.1 — 2026-11-02

Upgrade: Existing projects remain compatible. Rebuild and redeploy. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.29.0 — 2026-11-01

Upgrade: Existing projects remain compatible. Rebuild and redeploy. A document whose label differs from its name now shows the label under the title; a document that should not show one sets label to the same text as name.

0.28.1 — 2026-10-30

Upgrade: Existing projects remain compatible. Rebuild and redeploy. Author syntax for figures is unchanged.

0.28.0 — 2026-10-29

Upgrade: Existing projects remain compatible. Rebuild and redeploy to get the figure widget. A site that already carries its own copy of a figure runtime script in its documents must remove it, or step figures and run boxes get two sets of controls. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.27.0 — 2026-10-29

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the larger text, the body font change and table sorting. Text struck through with a single ~ on each side needs ~~ now. CLI commands, configuration and Node.js requirements are unchanged.

0.26.3 — 2026-10-28

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the new card type. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.26.2 — 2026-10-28

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the new heading sizes, lines, code font and diagram style. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.26.1 — 2026-10-27

Upgrade: Same package as 0.26.0, which was tagged but never published to npm because the release check failed. Install this version.

0.26.0 — 2026-10-27

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the diagram theme and the label fix. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.25.0 — 2026-10-27

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the heading chips. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.24.0 — 2026-10-27

Upgrade: Existing projects remain compatible. The status configuration accepts two more kind values, refs is a new optional key, and hash links to missing headings now print a build warning. Rebuild and redeploy to apply the new badge and chip styles. CLI commands, document syntax and Node.js requirements are unchanged.

0.23.2 — 2026-10-27

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the new code colors, date labels and heading spacing. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.23.1 — 2026-10-27

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the figure border. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.23.0 — 2026-10-27

Upgrade: Existing projects remain compatible, except that a document whose frontmatter already uses created or revised for anything other than a YYYY-MM or YYYY-MM-DD date now fails the build; earlier versions ignored both keys. Rebuild and redeploy to apply the new figure and Details layout. CLI commands, configuration and Node.js requirements are unchanged.

0.22.1 — 2026-10-27

Upgrade: Existing projects remain compatible. Only package metadata and documentation links change. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.22.0 — 2026-10-26

Upgrade: Existing projects remain compatible. Sites without locales render as before, except that sitemap.xml now declares the xhtml namespace on <urlset>. To add a translation, set locales in the configuration and put its README.md and public folder under content/<code>/.

0.21.1 — 2026-10-26

Upgrade: Existing projects remain compatible. Rebuild and redeploy to apply the desktop navigation spacing. CLI commands, configuration, document syntax and Node.js requirements are unchanged.

0.21.0 — 2026-10-23

Upgrade: Existing projects remain compatible. dev and preview still listen on localhost unless --host or host is set. The build output, document syntax and Node.js requirements are unchanged.

0.20.0 — 2026-10-23

Upgrade: Rebuild and redeploy for the narrower layout and new 404 screen. statusImage is optional. If an older .cloudflare/prepare.mjs copies 404.html unconditionally, remove that copy or copy only when the output is absent; keep _headers preparation. Rename any document that would generate /404.html/, such as public/404.html.md, because 404.html is now reserved. Node.js requirements and the other existing CLI and configuration options are unchanged.

0.19.0 — 2026-10-23

Upgrade: Existing projects remain compatible. The dev, build and preview commands, configuration, document syntax and Node.js requirements are unchanged. New sites can select Cloudflare Workers during init; existing Cloudflare Pages and GitHub Pages setups remain supported. Rebuild and redeploy to include the first-paint fix.

0.18.0 — 2026-10-22

Upgrade: Existing projects remain compatible. The dev, build and preview commands, configuration, document syntax and Node.js requirements are unchanged. New projects can start with for-humanity init instead of copying the template.

0.17.0 — 2026-10-22

Upgrade: Existing root deployments remain compatible. For a GitHub project site, set basePath: "/repository/" and keep url as the origin, such as https://username.github.io. Rebuild and deploy the contents of content/dist.

0.16.0 — 2026-10-21

Upgrade: CLI commands, configuration, document syntax and Node.js requirements remain compatible. Document pages now use each label as their description, so write labels that read well in search results and link previews. Pages are still marked as Korean by default; set lang, such as lang: "en", for sites in other languages.

0.15.0 — 2026-10-21

Breaking change: The build now fails, with the file and line, on input that earlier versions accepted: a ::part without a plain-text title, with attributes or without a ## section before the next part; a selected snippet region without an end marker; a non-image file such as a PDF in a Markdown image, <img>, srcset or poster; a raw HTML <video>, <audio> or <source> that points to a missing local file or to a format other than MP4, WebM or MP3; a raw HTML <track>, <embed> or <object> that points to a missing local file or to a format other than WebVTT, PDF or an image; and a raw HTML <h1> or <h2> inside a Note or Details block. Write each part as ::part[Title] followed by a ## section, add the missing end marker, link non-image files instead of embedding them, add missing media files, convert other media to MP4, WebM or MP3 or serve it from an absolute or external URL, and move raw <h1> and <h2> headings out of Note and Details blocks. See the 0.15.0 migration steps.

Upgrade: CLI commands, configuration and Node.js requirements remain unchanged. Run build after updating and fix each reported file and line; the new link warnings do not stop the build. Raw HTML <h2> and <h3> headings now get anchors, so a later Markdown heading with the same text gets a -1 suffix. Sidebar scroll positions saved by older versions start from the top once.

0.14.2 — 2026-10-20

Upgrade: CLI commands, configuration, document syntax and Node.js requirements remain unchanged.

0.14.1 — 2026-10-19

Upgrade: CLI commands, configuration, document syntax and Node.js requirements remain unchanged.

Known issue: The intermittent Windows cursor check (NAV-010) fails again in CI, and its cause is being investigated. See Maintenance.

0.14.0 — 2026-10-19

Breaking change: Configuration now belongs in the project root. CLI paths identify a project, not a Markdown folder. Move published documents into content/public, local-only documents into content/private, and the site home into content/README.md; use content.root, content.public and content.private to customize these paths. Existing flat document folders are not automatically published. See the migration guide. Node.js 22.12.0 or later is still required.

0.13.1 — 2026-10-16

Upgrade: CLI commands, configuration and Node.js requirements remain unchanged. Navigation scroll positions saved by older versions may reset once after upgrading.

Known issue: The previously recorded intermittent Windows cursor check (NAV-010) remains deferred. See Maintenance.

0.13.0 — 2026-10-16

Upgrade: Node.js 22.12.0 or later is now required; upgrade Node before installing. Existing dev, build, preview commands and .mjs configurations remain supported. To use typed configuration, replace the .mjs file with for-humanity.config.ts; keep only one configuration file per document folder. Development and preview servers bind to localhost.

Known issue: The Windows browser check for cursor visibility after a reload (NAV-010) intermittently fails. The other browser checks and installed-package dev/preview checks pass; further cursor lifecycle investigation is deferred. See Maintenance.

0.12.0 — 2026-10-13

0.11.0 — 2026-10-13

0.10.0 — 2026-10-13

0.9.1 — 2026-10-13

0.9.0 — 2026-10-13

0.8.1 — 2026-10-13

0.8.0 — 2026-10-13

0.7.1 — 2026-10-11

0.7.0 — 2026-10-06

0.6.0 — 2026-10-04

0.5.0 — 2026-10-04

0.4.4 — 2026-10-04

0.4.3 — 2026-10-04

0.4.2 — 2026-10-04

0.4.1 — 2026-10-04

0.4.0 — 2026-10-04

0.3.0 — 2026-10-04

0.2.1 — 2026-10-04

0.2.0 — 2026-10-04

0.1.2 — 2026-10-03

Documentation and release automation update. The CLI commands and Node.js requirement are unchanged.

The v0.1.1 attempt stopped during package validation and was not published to npm.

0.1.0 — 2026-10-03

First public release of the Markdown documentation CLI. Requires Node.js 22 or later.

init, search and deployment under a URL subpath are planned. Static output currently assumes the site root /.