Skip to content

v0.6.1

Choose a tag to compare

View all tags
@jesshart jesshart released this 23 Apr 18:11
· 10 commits to main since this release
v0.6.1
efa763a

Fixed

  • Parser: documentation-about-syntax no longer parses as usage.
    [[id:X]] and [text](path.md) inside fenced code blocks
    (``` or ~~~), inline code (any matched backtick run), or
    backslash-escaped brackets/parens (`[`, `]`, `(`, `)`) are
    now treated as literal text by every ref-handling site — `check`,
    `init --adopt` (including the auto-filled `links:` and the MIGRATE-
    gate), `molt`, `rename-id`, and `refs`. Docs that teach croc's
    syntax no longer materialize spurious `to: X` frontmatter entries,
    trip `E-DANGLING` / `E-LIFETIME` / `E-IDENTITY`, or get their
    syntax examples rewritten on molt. A ref written as documentation
    survives the full adopt → molt round-trip byte-for-byte.

Release-process fix

Prior releases from v0.4.0 through v0.6.0 all have the literal
string "vX.Y.Z" as their GitHub Release body because the tag was
annotated with -m vX.Y.Z and gh release create --notes-from-tag
copies the tag annotation verbatim. The Makefile and README release
recipes now document the correct form: git tag -a vX.Y.Z -F notes.md
so the annotation carries real content.

Assets 2
Loading