Repository navigation
Ingest, publish and promote product release candidates - #27
Merged
Merged
Conversation
The Distribution Hub contract had no path from a source build to a release. The Ingest release workflow takes a registered product and the run id of its candidate build, verifies every identity in the candidate (catalog, source tag and commit, successful main build, digests, SHA256SUMS, CycloneDX SBOM, provenance and SBOM attestations, macOS notarization), publishes it under the product's namespaced tag without moving the repository-wide latest release, and can move a channel. Source repositories are public, so the candidate is read with this repository's own token; no cross-repository credential exists. scripts/verify.py now exercises the rules on a synthetic candidate.
The documentation contract has failed on main since the distribution hub landed: 'distribution' and 'compatibility' are not supported feature kinds. Every surface now names its verification command.
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.
Implements Phase 3 of
docs/DISTRIBUTION.mdfor the first product, Flyto2 Runtime.Ingest release (
.github/workflows/ingest-release.yml,workflow_dispatch:product,source_run_id,promote):products/catalog.json.*-candidateartifact with this repository's own token. Source repositories are public, so no cross-repository credential is needed; this was probed before relying on it.scripts/ingest_release.py verify: manifest schema, catalog identity, namespaced tag, channel vs. version, source tag → commit, run repository/id/workflow/commit/branchmain/conclusionsuccess, every digest and size,SHA256SUMScovering every file, CycloneDX SBOM, native signing evidence.gh attestation verifyon each installer against the shipped provenance and SBOM bundles, pinned to the source repository, its workflow and commit, no self-hosted runners.stapler validate,spctlon the disk image and the app inside (source=Notarized Developer ID).<prefix>X.Y.Zwith--latest=falseso the legacy Flow/releases/latestalias does not move. An existing tag is accepted only when its manifest is byte-identical.promoterewrites the channel JSON (and for stable, the product page downloads block) and pushes it tomain.scripts/verify.pygains an ingest self-test: 1 accepted candidate, 5 tampered variants refused, promotion on a copy. The documentation workflow installsjsonschemafor it.The Runtime side (candidate bundle from
flyto-runtime's macOS App workflow) lands in flytohub/flyto-runtime.Verified locally:
python3 scripts/verify.py,git diff --check,flyto-index verify . --full-scan --strict. Not yet verified: a real ingest run, which needs this onmain.🤖 Generated with Claude Code