Skip to content

fix(report): label package versions - #1614

Open
John-David Dalton (jdalton) wants to merge 2 commits into
fix/scan-report-text-v1xfrom
jdalton/report-version-v1x
Open

John-David Dalton (jdalton) wants to merge 2 commits into
fix/scan-report-text-v1xfrom
jdalton/report-version-v1x

Conversation

@jdalton

@jdalton John-David Dalton (jdalton) commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Label the package version value as Version in text and Markdown scan reports.
  • Keep the existing unknown-value fallback and add renderer coverage for folded and multiple-version output.

Validation

  • Renderer unit tests, type build, scoped lint, and format checks passed.

Note

Low Risk
User-facing column rename and field rename on flattened rows only; version resolution logic is unchanged.

Overview
Scan report output now labels the third alert-table column as Version instead of Introduced by, and flattened alert rows expose packageVersion (same value as before, still keys[2] or <unknown>).

Plain-text tables use a VERSION header; Markdown tables and flat row objects use Version. JSON report shape is unchanged aside from test fixtures that reflect deeper nested alert maps.

Tests were updated for the new labels and add coverage that version strings stay correct across version, file, and package fold modes and when multiple versions appear.

Reviewed by Cursor Bugbot for commit fe7d1a8. Configure here.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant