Repository navigation
ops: read-only release tracking, production probe and D1 query scripts - #658
Merged
Merged
Conversation
…ripts release-status.sh follows a release through Release, rel/ marker, deploy commit, deploy CI and both production deploys (with the Feed plan), matching workflow_run deploys by start time because they report main's SHA. Superseded deploy commits that never finished fall back to the older commit that deployed the version. probe.sh checks the 20 key production paths. d1-read.sh runs one read-only statement against production D1 and rejects writes. These replace hand-written monitors that broke repeatedly during the repository split. The runbook, deployment.zh.md and the AGENTS.md index point at them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AsperforMias
requested review from
KurosawaGeeker and
hikariming
as code owners
November 8, 2026 15:36
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
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.
Adds three read-only operator scripts in
.github/compose/:release-status.sh [--wait] <repo> vX.Y.Zrel/marker → deploy commit → deploy CI → apps and Cloudflare deploys, and reports the Feed plan. Exits 0 deployed, 1 failed, 2 in progress.probe.sh [origin]d1-read.sh core|feed "SELECT …"PRAGMA x = y.Why: during the repository split, release monitoring was written by hand four times, and each version broke. The worst case: filtering deploy runs by the deploy commit's SHA never matches, because
workflow_rundeploys report main's SHA.release-status.shmatches deploy runs by start time instead. If the newest deploy commit pinning a version was superseded before it finished, the script falls back to the older commit that actually deployed it.Verified:
release-status.shagainst real releases:ghfind v1.0.3,ghfind-server v1.0.5andghfind-frontend v1.0.2report deployed.ghfind-server v1.0.4reports deployed via its earlier commit, not the cancelled superseding one.v9.9.9reports pending.probe.sh: 20 of 20 paths return 200.d1-read.sh: reads succeed, and four write attempts are rejected.The runbook (SYNOPSIS, release, FILES),
deployment.zh.mdsection 11 and theAGENTS.mddocument index now point at these scripts. There's no deploy impact, so this needs no release.🤖 Generated with Claude Code