v0.5.0

• chore: prepare forge-template 0.5.0 (#173)
• test: validate provider parity, reproducibility and distributions (#172)
• feat: implement reproducible rendering for engine updates (#153)
• feat: ship the approved generated-content capabilities (#152)
• feat: implement the github platform component (#151)
• feat: implement provider provenance and public metadata contracts (#150)
• docs: define provider compatibility, failure and release gates (#149)
• docs: define platform composition and generated-tooling parity (#148)
• docs: define generation provenance and reproducible-update inputs (#147)
• docs: inventory default-Copier parity and assign ownership (#146)
• docs: record filed cross-repository roadmaps
• docs: prepare engine-default and Streamlit roadmap packs
• chore: add bounded uv dependency updates for forge-template
• docs: reconcile living provider documentation with the 0.4.1 release
• docs: simplify template README and improve feedback routes (#135)
• docs: reconcile the cross-repository matrix after the create-forge 0.3.0 release (#134)
• docs: complete Stage 14 release

---

Existing projects can pull this in with uvx copier update --trust.

v0.4.1

• chore: prepare forge-template 0.4.1
• test: validate the cross-repository Data Science line
• test: validate three-archetype composition boundaries
• docs: complete Stage 12 release

---

Existing projects can pull this in with uvx copier update --trust.

v0.4.0

• chore: prepare forge-template 0.4.0
• test: validate Data Science generated projects at both Python endpoints
• feat: add the Data Science notebook and artefact layout
• feat: implement the Data Science archetype
• test: validate production capability composition
• feat: implement the Scientific Python capability
• feat: implement the Jupyter capability
• feat: publish Foundation extension points for capability tooling
• docs: define Data Science compatibility and acceptance strategy
• docs: define notebook, data, and model safeguards (#119)
• docs: define initial Data Science capability contracts
• docs: define Data Science project shape and ownership
• docs: triage Data Science roadmap issues
• docs: define Data Science archetype roadmap
• docs: split the template invariants out of CLAUDE.md
• chore: add markdownlint to the pre-commit gate
• test: validate no-copy inheritance model
• docs: define Forge-Blueprint compatibility policy
• test: add generic downstream policy reference fixture
• docs: define safe override and extension points
• docs: define organisation policy model
• docs: complete Stage 08 architecture review

---

Existing projects can pull this in with uvx copier update --trust.

v0.3.2

• refactor: align Foundation composition boundaries

---

Existing projects can pull this in with uvx copier update --trust.

v0.3.1

• chore: publish the engine to PyPI as an installable distribution (#86)

---

Existing projects can pull this in with uvx copier update --trust.

v0.3.0

• docs: record the v0.3.0 release state
• feat: implement the CLI Application reference archetype
• feat: add neutral Foundation pyproject extension points
• docs: define CLI application archetype contract
• feat: migrate the Library archetype to the composition contract
• feat: implement composition protocol 2 and rendered output paths
• docs: define Library archetype contract
• docs: sync cross-repository dependency matrix
• feat: add generated-project validation
• feat: expose stable template-engine API
• test: create composition contract tests
• feat: design the template variable contract
• feat: define file conflict and override rules
• feat: define deterministic composition order
• feat: define component manifest protocol v1
• feat: define ProjectSpec protocol v1
• ci: bump actions/checkout from 4.4.0 to 7.0.1 (#69)
• ci: bump astral-sh/setup-uv from 5.4.2 to 10.0.1 (#68)
• ci: pin GitHub Actions to immutable commits
• docs: plan SBOM and release provenance capability
• feat: add secret-handling safeguards
• docs: close Stage 04 epic
• docs: define exception ownership conventions
• docs: define path and resource ownership conventions
• docs: define structured logging capability
• docs: define environment-variable conventions
• docs: define configuration ownership conventions
• docs: reconcile cross-repository dependency mirror
• docs: define optional editor integration strategy
• docs: link cross-repository contributor workflow
• docs: accept public engine integration target
• docs: define Python support policy
• docs: define Foundation scope boundaries
• docs: define Forge Foundation guarantees
• docs: define Forge architectural terminology
• chore: sync shared label taxonomy
• docs/roadmap and issue creation (#49)
• chore: shared label taxonomy with create-forge (#10)
• docs: adopt a branch and pull request workflow
• fix: set git identity via config, not env vars, in the test fixture
• refactor: port test-combos.sh/test-update.sh to a pytest suite
• docs: add ADRs for decisions already made, checked by src/forge_template/adr.py

---

Existing projects can pull this in with uvx copier update --trust.

v0.1.1

• feat: add root repo tooling, docs, and a pre-commit lint gate
• fix: trailing newlines in 5 template files missed by prior invariant-1 guard
• docs: record the local-green-vs-CI-green lesson from this release
• fix: two more CI-only bugs surfaced now that lint/git-identity are fixed
• fix: configure git identity in CI before scaffolding
• fix: resolve shellcheck failures that were blocking CI's lint job
• docs: link CLAUDE.md backlog to filed follow-up issues, mark v0.1.0 shipped

---

Existing projects can pull this in with uvx copier update --trust.

v0.1.0

Initial release.

---

Existing projects can pull this in with uvx copier update --trust.