docs: document main-only auto-tagged promotions
All checks were successful
CICD / Build and Push CICD Images (pull_request) Successful in 11m48s
CICD / Build CICD Image Failure Postmortem (pull_request) Has been skipped
CICD / Source Checks (pull_request) Successful in 5m30s
CICD / Source Lanes Failure Postmortem (pull_request) Has been skipped
CICD / Build Release Images (pull_request) Successful in 7m19s
CICD / Dependency Audits (Informational) (pull_request) Successful in 18m7s
CICD / CICD Tests Complete (pull_request) Successful in 5s
CICD / Build Tester Images (pull_request) Successful in 6m40s
CICD / Production Image Failures Postmortem (pull_request) Has been skipped
CICD / Production Images Complete (pull_request) Successful in 5s
CICD / Runtime Black-Box Integration Tests (pull_request) Successful in 20m21s
CICD / Integration Tests Failure Postmortem (pull_request) Has been skipped
CICD / End-to-End Tests (pull_request) Successful in 39m58s
CICD / E2E Tests Failure Postmortem (pull_request) Has been skipped
CICD / Promote Staging Images To Release (pull_request) Has been skipped

This commit is contained in:
copilotcoder
2026-07-17 15:54:56 -04:00
parent 16d6569acd
commit f1a32f20c0
4 changed files with 21 additions and 15 deletions

View File

@@ -75,16 +75,18 @@
- `deployable-backend-staging`
- `deployable-frontend-staging`
- Runtime validation (`Runtime Black-Box Integration Tests` and `End-to-End Tests`) must pass before release tagging.
- `Promote Release Images` retags validated staging artifacts to release repositories:
- `Promote Release Images` retags validated staging artifacts to release repositories, but only on automated `push` runs to `main`:
- `deployable-backend`
- `deployable-frontend`
- Published release tags:
- `latest`
- `<semver>`
- `<semver>-<7-char-short-sha>`
- `v<major>.<minor>.0`
- `v<major>.<minor>.<patch>`
- `v<major>.<minor>.<patch>-<7-char-short-sha>`
- Version selection rule:
- If HEAD has a semver git tag (`vX.Y.Z`), use it.
- Otherwise, auto-increment patch from the latest semver baseline for that major/minor line.
- If the qualifying `main` commit already has a semver git tag (`vX.Y.Z`), use it.
- Otherwise, auto-create and use the next patch tag from the latest semver tag in the repository.
- If no prior semver tag exists, bootstrap from `v0.0.0` and create `v0.0.1`.
- Dependency audits are informational: frontend and backend audit steps both run and do not fail the full workflow.
### **Working Component Integration**