Repository navigation
Release record R2: draft notes and owner, release modes, sign-off - #91
Merged
Merged
Conversation
- Next release card: a "Notes and owner" editor (Keep a Changelog sections, known issues, rollback notes, owner, risk), saved by the backend as a direct commit to the app repo's glidepath/releases/next.yaml and sealed into the record when the release reaches Flight. "Fill empty sections from the merged PRs" pre-fills notes from the scope. Readiness gains release notes, release owner and, for Hand-flown apps, sign-off. - Release mode bar on the Record tab: Hand-flown / Assisted / Autoland (Autoland shown, not available yet). Admins change it with a PR to the platform-owned release-modes file. - Record detail: a "Release notes and sign-off" panel (the sealed notes, and the sign-off on the production release PR: from the record, else live). The confidence score's approval points now come from sign-offs that count (before the merge, not by the merger); human-context approvals are shown as acknowledgements after release and earn nothing. Export carries both. - Masthead: the app name moves to the kicker (it read as part of the title next to the release name), and the full image reference and digest show. Needs the matching backstage routes (/release-draft, /release-mode, /release-signoff). Docs: docs/release-records.md, docs/security.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
R2 of the Release Record work. This needs jfillman/backstage#136 for its routes.
glidepath/releases/next.yamlin the app repo. The record takes the draft when the release reaches Flight.release-modes.yaml.imageRepo.docs/release-records.md(modes, sign-off, draft) and the permission table indocs/security.md.Verified
tsc, lint andyarn ratchetare clean. All 794 tests pass, including new tests for the editor, mode bar, sign-off panel, note suggestions and the readiness checks.ghcr.io/jfillman/boarding-api:1.1.2-f59127cfor a superseded record.Not exercised live
These were left out on purpose, because they make real commits and PRs:
They're covered by unit tests on both sides.
🤖 Generated with Claude Code