Repository navigation
fix(report): validate nested and rendered public metadata - #33
Merged
Merged
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.
Change
Public reports now inspect nested JSON, rendered encodings and named credentials before sending. Rootform repository reports reject private workspace references while reports for other repositories retain their existing path policy. Exact synthetic provider values remain valid. This completes the reporting privacy boundary in SPEC-006.
Validation
bun run verifypassed, including runtime and tooling tests, workflow analysis, secret scans and reproduction of the committed Action bundle. Encoded credential, nested metadata and consumer path-policy cases pass. Published-release integration remains a post-publication check.