Skip to content

ops: deploy v3.0.0 report (LIVE_WITH_NON_CRITICAL_ISSUES)#63

Merged
Apolloccrypt merged 1 commit into
mainfrom
ops/deploy-report-v3.0.0-20260527
May 27, 2026
Merged

ops: deploy v3.0.0 report (LIVE_WITH_NON_CRITICAL_ISSUES)#63
Apolloccrypt merged 1 commit into
mainfrom
ops/deploy-report-v3.0.0-20260527

Conversation

@Apolloccrypt
Copy link
Copy Markdown
Owner

Autonomous deploy execution result for v3.0.0.

Status: LIVE_WITH_NON_CRITICAL_ISSUES | Smoke exit: 1 (CRITICAL=0, no rollback)

Result

Non-critical issues (root cause: static frontend not synced)

nginx serves /.well-known/ + static pages from /home/paramant/app (a non-git
artifact dir) and / from a :8080 host service. The authorized compose-dir
deploy updated only the relay/admin backend, so:

Remediation (NOT done autonomously - outside the authorized deploy scope): sync
the static frontend artifact to /home/paramant/app, then re-run the smoke test.

Rollback readiness

Not triggered. All 6 service images tagged + manifest written for
scripts/rollback-3.0.0.sh (/home/paramant/backups/rollback-images-latest.txt).

Full report: docs/audit-reports/deploy-v3.0.0-20260527-2304.md.

🤖 Generated with Claude Code

Backend live on 3.0.0, R006 core crypto confirmed (1 KEM ML-KEM-768).
Smoke exit=1 (CRITICAL=0, no rollback). 3 non-critical failures all trace
to the static frontend root (/home/paramant/app) not being synced by the
compose-dir deploy; remediation noted for follow-up.

Backup stamp: 20260527-2304

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Mick Beer <mick@paramant.app>
@Apolloccrypt Apolloccrypt merged commit ffb04a8 into main May 27, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant