Repository navigation
Release record polish, builds vs releases, honest supply chain, Release flows filter - #95
Merged
Merged
Conversation
…cord's colour strip; credentials docs: actor tokens aren't pod-bound - PromoteDialog: one line on what happens, one on when the environment changes; errors say what failed in a sentence, with the raw API error under Details. - RecordColumn: the record's panel look (3px strip, uppercase title, ruled head) for the panels in their own files. Outcome's strip follows the outcome (green clean, red rolled back, amber replaced before healthy, blue baking); Release notes and sign-off is amber, like the human context it sits beside. - docs/credentials: tower-actor tokens are no longer bound to the pod (backstage#140). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Human context becomes After release: how it was checked in production, follow-ups (new) and acknowledgements. The summary moves into the draft (written before the release ships) and leads Release notes, the changelog, the export and the GitHub Release body. Records from before the draft carried summary and risk can still be given them under After release; a newer record's after-the-fact summary or risk shows in Release notes, marked as such. - Builds vs releases: the Matrix's rows are builds, and a build that shipped to Flight shows its release name. Promote names the release it is promoting, or says which release an unnamed build becomes once healthy in Flight. - Docs: release-records, architecture, components, security. Needs the backstage change that adds the draft summary and the followUps field. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hat it means and what to do
Found live (boarding-api 1.1.3, pre-prod): Build, SBOM, Signature and Rekor went green as soon as the item existed,
and Sign + Attest went green when any one attestation verified, so a step could be green while its own detail said
"did not verify". The details showed raw sigstore errors ("inclusion promise could not be verified", "expected
1 timestamps, got 0") with no meaning or next step.
- supplyChain.ts: one rule for every view. Green verified; amber present but unverified for a reason that is not
evidence of tampering; red contradicted (another log entry, another image's digest, a bad signature); grey missing.
Reads the backend's verificationCode, else infers it from the message.
- Plain words per result: what Tower found, why, and what it means for the release.
- Roll-ups (Sign + Attest, Rekor) say n of m verified and explain the weakest one.
- "Signed and attested" (readiness +15, the record, the Command Deck, the export, the next release's readiness)
is now: build provenance verified and nothing contradicting it, not "any attestation verified".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Found live (boarding-api): Tower's Promote and Roll back run the release Pipeline labeled hangar.io/flow=promote / rollback, and the filter matched only 'ci', so Release flows showed none of them. Any labeled flow that isn't a preview build or a guardrail is now a release flow, which also covers a cicd.yaml's own flow names. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jfillman
changed the title
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.
Fixes and features from the R1–R4 test run, plus the supply-chain review. Needs backstage#141. Merge, release, then bump the pin in #141 so everything ships in one build.
1. Promote dialog, in plain words.
1.1.4-9d3dcde, now in staging."3. Human context becomes After release
4. The record's Outcome and Release notes and sign-off panels get the record's own panel look (
RecordColumn.tsx).5. Builds vs releases.
Supply chain (
supplyChain.ts)A step's colour now means verified:
Before, Build, SBOM, Signature and Rekor turned green as soon as the item existed, and Sign + Attest turned green when any one attestation verified.
Every result says what it means and what to do, from the backend's
verificationCode. Raw sigstore messages are gone."Signed and attested" has one definition everywhere: the build provenance is verified and nothing contradicts it. This covers the readiness +15, the record, the Command Deck, the export and next-release readiness.
Pipelines (bug): Release flows now includes Tower's promote and rollback runs (
hangar.io/flow=promote/rollback).Docs:
supply-chain.md(new)release-records(builds vs releases, After release)credentials(actor tokens aren't pod-bound)architecture,components,securityVerified:
tsc, lint andyarn ratchetare clean, and 818/818 tests pass.🤖 Generated with Claude Code