docs(release): align channel and consumer guidance with current contracts - #110
Merged
Merged
Conversation
…acts Signed-off-by: rldyourmnd <danil@nddev.it.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
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.
Release guidance still described a private repository, claimed OIDC alone enabled private artifact attestations, referenced retired private pin ledgers, and treated per-profile runtime flags as a waiver for stable evidence. Align it with the actual hosted workflow and builder: separate build/attest/publish permissions, exact stable/frozen tags, mandatory signed active-seven evidence, provisional canary semantics, and per-module consumer pin policies.
Correct the dispatch input name to
harness_evidence_bundle_base64and remove stale fleet/private-repository workflow comments. Workflow behavior and permissions are unchanged. GitHub attestation availability is linked to current official documentation.Validation: actionlint; all selected hosted workflow, provider consistency and privilege-boundary tests; native projection check; diff check. No workflow dispatch, release, tag, install or consumer-policy relaxation is included.