Updates — Changelog & Release Notes
Status: Active
Last Updated: 2026-08-26
Category: Overview
Prerequisites: None
Tags: updates, changelog, releases, gitops
Summary
Every change to fogserv.cloud ships through Git, so the changelog is the release history. Recent posts are published via the CMS; the full commit-level history lives in the repository at git.shire.one/fogserv/website.
Where to Look
| What | Where |
|---|---|
| Published update posts | /changelog — CMS-driven, newest first |
| Commit-level history | Forgejo repo history |
| Project roadmap | tasks.md |
| Session-by-session learnings | lessons-learned, problems-solved |
How Updates Ship
- Change merged to
main(GitOps is Law) - CI builds → image pushed → cluster deploy picks it up (deployment-runbook)
- Notable user-facing changes get an update post via the CMS admin
Related
- Apps
- Rollback procedures — when an update goes wrong