Record the deploy state the pipeline reached - #26
Merged
Conversation
The backlog described the VPS as untouched and the deploy as proven on local mirrors alone, which stopped being true once the pipeline deployed staging end to end. The remaining work is narrower than the old list implied, and the part that matters is unproven rather than undone: a pipeline deploy that fails part way has never been shown to leave the site serving. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates TODO.md to reflect the current, observed deploy state now that deploy-site.yml has successfully deployed staging end-to-end from CI, and to replace completed “next steps” with the remaining unproven/unfinished work (notably: demonstrating rollback behavior through a failing pipeline run).
Changes:
- Refreshes the “State” section to record that staging has been deployed by pipeline and is live behind an auth gate.
- Updates the release/deploy pipeline entries to reference the newest prerelease and the existence of a dispatchable staging deploy workflow.
- Rewrites the “Next” list to focus on proving rollback behavior via pipeline and performing a first non-live production deploy.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Session state, committed rather than left in a session that ends.
What changed
The state table said the VPS was untouched and the deploy was proven on local mirrors alone. Both stopped being true when
deploy-site.ymldeployed staging end to end from CI: build, stamp, upload through the confined key, symlink flip, in-process reload, and the full 1,245-URL contract verified against the live site behind the auth gate.The next-steps list also carried four items that are done: provisioning, the confined key and its deploy roots, the staging DNS record and its Pangolin resource, and writing the deploy workflow.
What remains, stated as what is unproven
The interesting entry is not a missing feature. A pipeline deploy that fails part way has never been shown to leave the site serving. The server side has been measured by hand at well under a second to roll back, but the two-phase upload-then-flip has not been exercised through a failing run. That is the difference between a design that should be safe and one that has been seen to be.
Production is configured and has never run, deliberately: its Pangolin resource is disabled and the record still points at the old platform.
🤖 Generated with Claude Code