core · Current reference
Core release checklist
Follow the implementation-side gates required before a Core release is tagged.
Applies to v0.2.4
Component pins for v0.2.4
| Component | Role | Version |
|---|---|---|
| core | runtime | v0.1.20 |
| theme-shield | theme | v0.1.15 |
| starter | reference | v0.1.3 |
| docs | reference | v0.1.4 |
| distribution | tooling | v0.3.2 |
| restricted-component-1 | consumer-reference | v0.1.10 |
| restricted-component-2 | consumer-reference | v1.1.21 |
The canonical release verification path is in VALIDATION.md.
Run before any release:
node scripts/foundry-doctor.js
For browser parity:
node scripts/foundry-doctor.js --browser-smoke --require-browser
For downstream consumer validation:
node scripts/foundry-doctor.js --site /absolute/path/to/site
See VALIDATION.md for the full regression review checklist and CI safety bar.
Administrative release steps
- Confirm
node scripts/foundry-doctor.jspasses clean. - Confirm the changed block, shell, flow, or SEO docs still match the current contract.
- If new blocks were added, confirm the block registry and block-family-manifest are updated.
- Tag the release (e.g.,
v0.1.20). - Update pins in downstream sites only when approved through the bundle process.