infraweaver/changelog
Changelog
The canonical record is CHANGELOG.md in the repository, kept in
Keep a Changelog format and written from merged pull requests. This page
summarises how it works and what is currently unreleased.
Unreleased
AddedInit UI verifies the applied-update path end to end: changelog display and restart into the new build.ADDED
FixedCluster Topology step now counts
hybrid nodes toward the control-plane minimum, so an all-hybrid cluster — even a single hybrid node — can proceed past Continue.FIXEDAnything that changes Kubernetes manifests records both the user-facing impact and the affected app or namespace, so a changelog entry is enough to know whether it touches you.
How releases work here
- Merged pull requests are the change recordThe changelog is written from them, not from memory at release time.
- The platform has no version number you installYou track a branch and pull. Components inside it have their own versions, pinned in their charts.
- The WordPress connector does have releasesIt ships on signed channels with its own version numbers, because it is installed into sites the platform does not own.
- Breaking changes are expected in alphaThey are documented rather than avoided. Read the changelog before pulling.
UPDATING SAFELY
$
git pull upstream main && bash scripts/generate-from-env.sh && git push onedev main
Re-running the generator after every pull is not optional: the committed template holds
${PLACEHOLDERS}, and skipping the step pushes those placeholders into the
repository ArgoCD reconciles from.