Repository navigation
[CI] Record validation provenance for aggregate CI result - #504
Closed
brandonpage wants to merge 1 commit into
Closed
brandonpage wants to merge 1 commit into
brandonpage wants to merge 1 commit into
Conversation
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
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.
Adds a terminal, per-attempt execution-provenance artifact to the PR validation entrypoint and an unfiltered PR integrity workflow. The aggregate publisher can verify the repository, PR, head/base commits, workflow revision, run and attempt without requiring individual matrix job names in branch rulesets.
The integrity workflow also provides initial metadata/syntax validation where no broad PR validation existed. Existing native CI remains part of the required validation policy.
This is a draft implementation. No ruleset is activated by these changes. Dedicated App installation, protected publisher deployment, workflow-ID enrollment, and live App/trust-boundary evidence are required before rollout. CI rulesets will remain in Evaluate mode.
Validation: generated workflows parse with PyYAML 6.0.4 and pass Actionlint 1.7.12; Zizmor 1.32.0 reports no findings in the new integrity workflows. Live Package fork fixtures verified successful provenance, pending/current reruns, rejection of an added workflow publishing an unrelated green
CI result, and propagation of real validation failure. The App itself has not yet been installed or used to publish checks.Publisher implementation: forcedotcom/SalesforceMobileSDK-Package#358
Target branch:
dev.