fix: Survive scanner findings in report-only mode #21
No reviewers
Labels
No labels
priority/P0
priority/P1
priority/P2
priority/P3
size/L
size/M
size/S
size/XL
size/XS
state/done
state/in-progress
state/in-review
state/needs-refinement
state/ready
type/bug
type/chore
type/feature
type/refactor
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
amtronics/platform-actions!21
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/security-scan-exit-codes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue
Refs #19
Problem
The launchpad canary run proved detection works (real js-yaml/markdown-it advisories found) but the job failed in report-only mode: the runner injects -e into shell: bash steps, so osv-scanner's exit 1 killed the step before the handling logic ran.
Solution
Capture every scanner's exit code inline (cmd && rc=0 || rc=$?) in all three steps.
Review notes
Re-run the launchpad canary security job after the v3 tag moves — it should report the findings and stay green.
Risks and trade-offs
N/A
WIP: fix: Survive scanner findings in report-only modeto fix: Survive scanner findings in report-only mode