Skip to content

chore: bump to 0.8.0-alpha.2 (post-publish bug fix) #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
PetriLahdelma wants to merge 1 commit into from
Closed

chore: bump to 0.8.0-alpha.2 (post-publish bug fix) #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [0.8.0-alpha.2] - 2026-05-25

> **Bug-fix release** on top of `0.8.0-alpha.1`. The `vertaa explain --copy | pbcopy` happy-path didn't actually work end-to-end against a real audit on `alpha.1` — three pre-existing issues surfaced post-publish and are fixed here. Install via `npm install -g @vertaaux/cli@next`. The stable `latest` tag remains at `0.6.2`.

### Fixed

- `vertaa audit URL --format json -o file.json` now writes addressable `ruleId` values for every issue. Most audits previously emitted `null` IDs on recommendation and IA findings, which meant `vertaa explain <id> --file file.json --copy` could not match findings by ID and the pipe-to-clipboard flow silently emitted nothing. (Audit-engine debt to retro-tag the underlying analyzers is a separate effort; the CLI now backfills synthetic stable IDs of the form `synthetic/<category>-<title-slug>-<idx>` at save and load.)
- `vertaa explain --file out.json` now reads the standard `{ data: { issues }, meta }` envelope shape that `vertaa audit --format json` writes. Previously you had to manually `jq '{ issues: .data.issues }'` before piping. The bare `{ issues: [] }` shape continues to work for backwards compatibility.
- Audit JSON's camelCase field names (`recommendedFix`, `wcagReference`, `businessImpact`, `impactScore`, `estimatedEffort`) are now first-class on the canonical `Issue` type. Previous releases only declared the snake_case variants, which led to silently-undefined values when consumers read the camelCase fields from the wire shape.

## [0.8.0-alpha.1] - 2026-05-25

> **Alpha release on the `next` tag.** The stable `latest` tag remains at `0.6.2`. Install this alpha via `npm install -g @vertaaux/cli@next` or pin to `@vertaaux/cli@0.8.0-alpha.1`.
Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@vertaaux/cli",
"version": "0.8.0-alpha.1",
"version": "0.8.0-alpha.2",
"description": "Run automated UX audits, accessibility checks, and performance analysis from the terminal or CI pipelines. Supports policy gating, SARIF output, and multi-page crawling. See https://github.com/VertaaUX/cli#readme for full docs.",
"type": "module",
"main": "dist/index.js",
Expand Down