Cutover runbook: record pre-flight P4 and P5 - #268
Merged
Merged
Conversation
P4: main at 88a44e8 (with #264) is now on Render, so the cutover only changes the host. P5: GitHub sign-in uses a separate OAuth App (Ov23lircpdsFt5nH2XYe) with a single callback URL, so it changes in step 3, which now names it; the Linear callback is already registered. verify-action#3 is already merged to the action's main (v1 unmoved), so step 5 is tagging only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
DevAsign Code Review
No issues found
✅ Merge score: 100/100
5 of 5 acceptance criteria met.
This is a documentation-only change to backend/deploy/gcp/CUTOVER.md recording the results of pre-flight steps P4 and P5 (plus updating P6/step 5 wording).
Tests: 0 passed, 1 unverifiable — see the "Tests by DevAsign" comment.
Contributor
Tests by DevAsign
0 of 1 criterion verified by tests, 1 unverifiable. Each verdict below links to its evidence. 5 — The change is limited to documentation under backend/deploy/ and does not modify application code. (unverifiable)Verdict: unverifiable No usable test plan was produced and the change is documentation-only, so no test exercised this criterion. |
This branch was successfully deployed
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updates
backend/deploy/gcp/CUTOVER.mdwith the pre-flight results. Documentation only; thedevasign-api-maintrigger ignoresbackend/deploy/**.P4: what ships ✅
mainat88a44e8(which includes #264) was deployed to Render. It booted at 2026-09-24 19:25:50Z, about 5½ min after that merge, withrowsLoadedAtBoot12598 (up from 11671) andwriteThrough:"ok". Render andapi:latestnow run the same backend code, so the cutover changes only the host.P5: OAuth callbacks ✅
Ov23lircpdsFt5nH2XYe, not thedevasign-agentGitHub App (Iv23lieE7A1ojKw01wDx). Render's live sign-in redirect confirms it. An OAuth App allows one callback URL, so it changes during step 3, and step 3's table now names the app by client ID.…/api/auth/linear/callbackon the Cloud Run host was added next to the Render one, so nothing changes at cutover except the Linear webhook URL (step 3).Verify action (P6 / step 5)
devasignhq/verify-action#3 is already merged to the action's
main. Customers aren't affected: they use@v1, which still points atfa565e1with the Render URL. Step 5 is now tagging only (v1.2.0, then movev1), and P6 warns against creating any verify-action tag before step 5.Left for the cutover owner: P7 (access to GitHub org admin, Stripe, Linear, both Vercel projects, Render) and P8 (a quiet window, and warning users they'll need to sign in again).
🤖 Generated with Claude Code