feat(release): remove release channels from the release pipeline - #179
Merged
Merged
Conversation
Release identity is the exact gds-v<version> tag, monotonic sequence, artifact and manifest digests, SBOM and attestation (ADR 0038). Channel fields stay optional for decoding documents produced while the field existed; a legacy channel is still checked against a consumer policy that lists it. - bundle.Build and gds-release-builder no longer take a channel or harness evidence, and every release must build from its exact tag. - release_sequence alone classifies a bundle: 0 is a development projection, >= 1 is a release. - the release workflow runs on pushes to main; the privileged resolve job derives the next version and sequence from the latest published envelope over the GitHub API without checking out candidate source, creates the tag, and hands the identity to the unprivileged build. - harness evidence remains a separately produced and verified estate/runtime signal; it gates adoption, not publication. - default_bundle_channel is removed from the estate schema and example.
The workflow step that materialized signed harness evidence into the release build was removed with the channel gate; the file tested only that step.
main repointed the caller to NDDev-OpenNetwork/ci-workflows in 3125062 but left the pin regex expecting the old github-actions path.
rldyourmnd
force-pushed
the
feat/remove-release-channels
branch
from
September 19, 2026 19:03
7d9fa06 to
17db8ed
Compare
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.
Summary
Removes release channels (
canary/stable/frozen/development) from the release pipeline per ADR 0038. Release identity is the exactgds-v<version>tag, monotonic sequence, artifact/manifest digests, SBOM and attestation;release_sequence == 0classifies development projections.bundle.Build,gds-release-builderand the release-candidate command no longer take a channel or harness evidence; every release must build from its exact tag.release-bundle.ymlnow runs on pushes tomain: a privileged resolve job derives the next patch version and sequence from the latest publishedrelease-envelope.jsonover the GitHub API — no candidate checkout — creates the tag, and hands the exact identity to the unprivileged build job.core/harnessevidence, module release evidence); it gates adoption, not publication, and no device signing key enters the release path.channel/allowed_channels/default_bundle_channelbecome optional decode-compatible fields for documents produced while they existed; a legacy channel is still checked against a consumer policy that lists it. The signed harness-evidence manifest payload keepschanneloptional so already-signed manifests still re-digest.Test plan
go test ./...— green on the committed tree (context/assurance/cli provenance tests verify committed lock consistency)scripts/validate_python.sh— 70 passedscripts/validate_shell.sh— PASS (8 scripts, shellcheck 0.11.0)scripts/validate_go_core.sh --quick— all modules verifiedmainpush after merge is expected to publishgds-v0.9.8automatically — verify resolve→build→attest→publish end to end