Repository navigation
Require completed EC evidence and exact component tags - #114
Merged
Merged
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dfarrell07 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
dfarrell07
changed the title
Collaborator
Author
|
The FBC-specific completion, exact snapshot selection and successful stage artifact checks are proposed separately in #117. Both changes retain completed warning/build-marker compatibility only with Finished/Passed conditions and scenario completion evidence; neither treats an unfinished marker as a pass. |
dfarrell07
force-pushed
the
clarify-skip-done-steps
branch
from
October 13, 2026 16:01
2fdbcf0 to
21cbda8
Compare
dfarrell07
changed the title
Share completed snapshot EC checks between the conductor and status helper. Require successful aggregate conditions and a completed unique EC result. Check all five exact component version tags with bounded queries, retain exact downstream scan requirements, and distinguish snapshot readiness from managed release policy in reuse guidance and tracker messages. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Daniel Farrell <dfarrell@redhat.com>
dfarrell07
force-pushed
the
clarify-skip-done-steps
branch
from
October 13, 2026 16:27
21cbda8 to
04afe63
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.
Unfinished enterprise-contract markers could advance release verification, and one source tag could cause status guidance to skip all CVE work. Require unique Finished/Passed aggregate conditions and completed enterprise-contract evidence, shared by autorelease and status reporting.
Check exact version tags on all five component repositories, with bounded queries. Missing tags and unavailable repositories cannot establish completed source work. Preserve immutable upstream tags while requiring downstream scan evidence for the exact snapshot and image identities. Guidance now distinguishes snapshot validation from managed release policy: reuse proven tasks, and repair demonstrated task, credential or trust failures without unrelated churn.
Validation: full
make testand mandatory commit hooks pass, including unfinished/failed/ambiguous evidence, completed warning/marker cases, exact snapshot selection and missing/unreachable/timed-out tag queries. Shellcheck, Markdown/YAML checks and gitlint pass. FBC-specific selection and publication checks are in #117.