packstruct docs

Release posts

One post per release, shaped like prestruct’s and crashtest’s posts - the format lineage is prestruct’s announcing-v1.0.0 and crashtest’s adopting batch. The post lives in docs/discussions/ as versioned source so the release trail sits in the same tree as the changelog it summarizes, and the file’s raw markdown IS the GitHub Discussions announcement - view source, copy, strip the frontmatter, post.

Prose on these pages flows - paragraphs keep their natural length, and nothing in the toolchain re-wraps them at commit time. Hard-wrapped prose is a commit-time artifact, and it dies at every reflow of an upstream forum renderer. Tables and frontmatter keep their own natural line lengths.

The conventions

The index

post version live
Announcing packstruct v1.1.2 1.1.2 2026-11-13 on npm
Announcing packstruct v1.1.1 1.1.1 2026-11-13 on npm
Announcing packstruct v1.1.0 1.1.0 2026-11-06 on npm
Announcing packstruct v1.0.0 1.0.0 2026-10-25 on npm (governed ladder, provenance)
Announcing packstruct v0.9.0 0.9.0 2026-10-24 on npm