Release Checklist
This chapter is a pragmatic checklist for documentation and parser changes before a release.
The important release posture is architectural:
parcreleases source/frontend behavior- it does not release binary or Rust-generation policy
- the tested
SourcePackagecontract matters more than parser-internal churn
Parser changes
Before releasing parser changes:
- confirm the smallest reproducer has a test
- confirm the intended flavor coverage is tested
- confirm the AST shape change is deliberate
- confirm visitor and printer behavior still make sense
Book changes
Before releasing documentation changes:
- confirm the affected public behavior is described in the book
- confirm unsupported or out-of-scope cases are still documented honestly
- confirm examples still match the actual public API names
Error-surface changes
Before releasing changes around errors:
- confirm structured fields still provide the needed information
- avoid treating formatted strings as the real contract
- update the error-surface chapter if the practical behavior changed
Workflow changes
Before releasing changes to the normal integration path:
- update the workflow chapter
- update the API contract chapter if the preferred boundary changed
- update stable-usage guidance if downstream posture should change
Artifact contract changes
Before releasing a SourcePackage shape change:
- confirm the changed field meaning is covered by contract-level tests
- confirm the consuming workflow examples still describe artifact boundaries
- confirm cross-crate composition is still described as tests/examples/harness work, not library coupling
Release gate
parc is ready to release only when:
make buildpassesmake testpasses- the canonical hardening surfaces are still green
- vendored musl
stdint - vendored zlib
- vendored libpng scan
- OpenSSL public wrapper extraction
- libcurl public wrapper extraction
- combined Linux event-loop wrapper extraction
- vendored musl
- deterministic repeated extraction still holds on the canonical large surfaces
- the book still teaches
parcas the source-meaning crate - unsupported or partial source behavior is still documented honestly
Final practical rule
If a change would force a downstream PARC consumer to rethink how it parses, traverses, or reports on source, the book should say so explicitly in the same change.