Repository navigation
Release record R1: next release draft, release names, Flight progress - #90
Merged
Merged
Conversation
…light progress The Record tab now opens with the release in progress, before any of it reaches Flight (Release Record proposal R1). Computed from data Tower already reads; nothing is saved. - Next release card: scope (source PRs merged after the previous release's commit landed), incoming open PRs, issues they close (GitHub closing keywords), candidate images built from main since, a suggested version (last version + the bump the PRs call for), and display-only readiness checks on the leading candidate. Promote sends it to the first Flight environment through the existing promote flow. - Release names: a tree per release, in order per app (ASPEN, BIRCH, CEDAR...), from the committed record history (new backstage /release-records route). A release whose record PR is still open is counted; one that never got a record is not, so names never shift when it leaves the window. - Each record shows how far it got through the Flight environments when an app has more than one (staging, pre-prod, prod). - A record's PRs are now bounded by when its commit landed on main, not by when it reached Flight, so a PR merged after the image was built no longer shows in a release that doesn't contain it. The draft uses the same boundary. - Flow slug mirror: 256 x 256 word lists, matching glidepath#109, with the same pinned chain-id -> slug vectors. Docs: docs/release-records.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
What
The Record tab opens with the release in progress, before any of it reaches Flight. This is R1 of the Release Record proposal: read-only and computed from data Tower already loads, with nothing saved.
/release-recordsroute). A release that reached Flight but never got a record stays unnamed, so later names never shift.docs/release-records.md(in the nav), plus the README/index highlights.Verified
tsc, lint andyarn ratchetare clean. All 783 tests pass, including new ones for the draft builder, names, the card, and the slug mirror.Not in this PR
🤖 Generated with Claude Code