Skip to content

Separate Starlink warnings and verify production smoke against the deployed commit - #72

Draft
ChevCellios wants to merge 2 commits into
masterfrom
codex/starlink-status-deployment-version
Draft

ChevCellios wants to merge 2 commits into
masterfrom
codex/starlink-status-deployment-version

Conversation

@ChevCellios

@ChevCellios ChevCellios commented Oct 8, 2026 •

Copy link
Copy Markdown
Owner

Starlink previously used one warning for stale orbital data and failed refreshes, while production smoke could pass against the previous healthy deployment.

Separate those warnings in HR/EN/DE, bake the build commit into assembly metadata through the Railway Docker build argument, and expose only that SHA at /version with no-store (503 for missing/invalid metadata). Uptime now waits for both liveness and the expected workflow SHA and rechecks it before success, preserving the 60-second backoff for HTTP 429. Docker CI verifies the SHA from the built container.

Validation for head 19784c8: 93 .NET tests and 27 Node tests passed locally and in CI; Docker build and embedded-SHA runtime verification passed. RESX XML, Bash syntax and diff checks passed. Security workflow passed, including CodeQL and NuGet/orbital JavaScript dependency audits. The separate Copilot AI findings check could not run because the monthly quota was exceeded (not a vulnerability finding).

CI: https://github.com/ChevCellios/Petabit/actions/runs/37824140389
Security: https://github.com/ChevCellios/Petabit/actions/runs/37824140388

No production workflow, deployment or merge has been initiated.

This branch has not been deployed

No deployments
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