Repository navigation
21 Deployment Landscape
Reviewed on 2026-11-05 against the GitHub repository and its workflow configuration.
GitHub has been the canonical development and publishing platform since 2026-09-05. Codeberg is a frozen archive.
| Destination | Source and automation |
|---|---|
| Source, issues, pull requests and releases | GitHub |
| CI and security analysis |
GitHub Actions, including ci.yml and codeql.yml
|
| PyPI and Docker Hub | release.yml, the single release publisher |
| mcpmemory.services | deploy-site.yml, deploying the site to Cloudflare Pages |
| GitLab | Push mirror of main; fast-forwards only, no tags or publishing secrets |
| Codeberg | Historical archive; no pushes, active CI or publishing secrets |
Use the repository's release workflow. A second publisher must not run alongside release.yml. The no-tags rule applies to the GitLab mirror, not to canonical GitHub: release tags belong on GitHub.
Historical Codeberg issue and PR links remain useful for the June-September 2026 period; they must not be rewritten to GitHub numbers. See the issue map.
The deployment diagram was authored on 2026-08-28. It describes the former Codeberg/Forgejo publishing topology and is historical, not the current deployment reference. The table above supersedes that topology.
- Architecture Diagram: runtime architecture.
- Repository operating conventions: hosting, mirrors and release rules.