core · preview
Core v0.1.45 release notes
Review the attribution wording, duplicate-render protection, and portable runtime cleanup in Core v0.1.45.
Applies to unreleased
Component pins for unreleased
| Component | Role | Version |
|---|---|---|
| core | runtime | v1.1.11 |
| theme-shield | theme | v0.1.15 |
| docs | reference | v0.1.6 |
| distribution | tooling | v0.3.24 |
Release date: 2026-07-30
This production patch updates the required page attribution to Built by Likestyle with Foundry, strengthens duplicate-render protection, and removes Hugo Blox-specific assumptions from the portable Foundry runtime.
Current Production Pin
Use v0.1.45 for new Core installations and production upgrades:
require github.com/jerrybroughton/likestyle-foundry-core v0.1.45
go install github.com/jerrybroughton/likestyle-foundry-core/cmd/foundry@v0.1.45
No content, configuration, database, dependency, or schema migration is required.
Attribution Contract
- The portable page hook now renders Built by Likestyle with Foundry and
keeps the existing
https://likestyle.com/foundry/destination. - The link remains visible by default. The existing fail-visible Foundry Control attribution decision contract is unchanged.
- Rendered quality validation fails when a content page omits the required link or versioned wrapper.
- Rendered quality validation also fails when a page contains duplicate attribution links or duplicate versioned wrappers, preventing site-local shadows or layout composition from rendering the badge more than once.
- Go tests, the Go quality contract, the Node quality backstop, and active attribution and SEO documentation use the same wording.
Portable Runtime Contract
- Shared hook and Tailwind partials now describe and implement Foundry-owned behavior without depending on Hugo Blox naming or resource conventions.
- Tailwind source discovery keeps site-local JavaScript, JSX, TSX, data, Hugo
stats, and generated Foundry safelist coverage without scanning an external
js/hbxresource namespace. - The Go runtime validator and legacy Node backstop reject Hugo Blox-specific
coupling if it is reintroduced under
layouts/. - Existing hook-collecting shells continue to work. Custom shells still call the documented Foundry hook partials explicitly.
Release Validation
The release uses the complete Release Checklist, including:
go test ./...
go run ./cmd/foundry authoring-contract --site . \
--core-version release-candidate \
--site-key foundry-core-release \
--commit-sha release-candidate
go run ./cmd/foundry validate quality
go run ./cmd/foundry validate compatibility-fixtures
go run ./cmd/foundry doctor --json
go run ./cmd/foundry release-check --json
node scripts/foundry-doctor.js
node scripts/validate-preview-runtime.js
node scripts/validate-workflow-contract.js
Repository GitHub Actions was disabled on 2026-07-30. The complete release
checklist is therefore run locally against the exact release tree. The retained
Ubuntu, macOS, Windows, and Safari workflow definitions are dormant and are not
claimed as executed v0.1.45 evidence; runner verification is deferred until
Actions is deliberately re-enabled.
See Foundry Core v0.1.44 for the article navigation interaction contract and shared-template adoption guidance.