fix: restore scanReport output#107
Merged
Merged
Conversation
cristof-ziel
previously approved these changes
Apr 16, 2026
cristof-ziel
approved these changes
Apr 16, 2026
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
2 participants
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.
Closes #104
The
writeReportfunction that set thescanReportaction output was removed in #89 (clean architecture refactor) without a replacement. ThescanReportoutput is still declared inaction.ymlbut was always returning an empty string.This restores the output by pointing it to
./scan-result.json, the file the CLI scanner already produces via--output=json-file=scan-result.json. Same data the old./report.jsoncontained, just without the redundant copy.