Skip to content

README status line: sections (0.7.1) - #19

Merged
llima merged 2 commits into
mainfrom
chore/readme-sections
Sep 29, 2026
Merged

llima merged 2 commits into
mainfrom
chore/readme-sections

Conversation

@llima

@llima llima commented Sep 29, 2026

Copy link
Copy Markdown
Owner

Summary

  • Version bumped to 0.7.1. Merging publishes craftar@0.7.1 to npm after approval in the npm environment. This is a README-only release, so the npm page shows the current status line.
  • The README status line (line 5) now names sections, which shipped in 0.7.0:
    • client-specific blocks in ingredient bodies, marked <!-- craftar:section <name> --> … <!-- /craftar:section -->;
    • overridden by a profile's sections and a workspace's overrides.sections;
    • each client's content is inferred by import;
    • a Forge that uses sections declares schema: 2.
  • craftar.dev checks its claims against this line; it already describes sections (Site parity with craftar-cli 0.7.0: sections craftar-cli-site#9).

Test plan

  • npm run typecheck: pass. npm run build: pass. craftar --version prints 0.7.1.
  • npm test (before the bump): 28 files passed, 1 skipped; 676 passed, 5 skipped. Oracle skipped (no fixture); there is no code change.
  • CI green on ubuntu and windows, Node 22 and 24.
  • node-cli-reviewer and docs-author reviewed the change: both clean, with one optional wording nit left as is.

0.7.0 shipped sections but the status line, which craftar.dev checks its claims against, did
not mention them.
@llima
llima merged commit f45cefa into main Sep 29, 2026
8 checks passed
@llima
llima deleted the chore/readme-sections branch October 4, 2026 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant