chore: bump to 0.8.0-alpha.2 + sync CHANGELOG#1
Merged
Conversation
Public mirror has drifted across multiple alpha releases (0.7.0-alpha.1 + 0.7.0-alpha.2 were published to npm but never synced here). This bump catches up to the current `next` tag at 0.8.0-alpha.1 with a sanitized CHANGELOG entry covering the user-visible Added + Fixed changes. The stable `latest` tag on npm remains at 0.6.2; this is an alpha-track catch-up only.
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Bumps the CLI to an alpha prerelease and documents the alpha release details in the changelog.
Changes:
- Update
package.jsonversion to0.8.0-alpha.1. - Add a
0.8.0-alpha.1changelog entry describing new features, fixes, and release notes.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| package.json | Version bump to the next alpha prerelease. |
| CHANGELOG.md | Documents the 0.8.0-alpha.1 alpha release contents and installation guidance. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ### Added | ||
|
|
||
| - `vertaa explain <findingId> --copy` — write the recommended fix for a specific issue to stdout, pipe-clean for clipboard tools. Use `vertaa explain X --copy | pbcopy` (macOS) or `| xclip -i` (Linux) to send the fix directly to your clipboard. Evidence rendering, step-list output, and the "Fix written to stdout" hint all go to stderr so they remain visible in your terminal without polluting the pipe. Emits a `finding_fix_copied` telemetry event. |
| ### Added | ||
|
|
||
| - `vertaa explain <findingId> --copy` — write the recommended fix for a specific issue to stdout, pipe-clean for clipboard tools. Use `vertaa explain X --copy | pbcopy` (macOS) or `| xclip -i` (Linux) to send the fix directly to your clipboard. Evidence rendering, step-list output, and the "Fix written to stdout" hint all go to stderr so they remain visible in your terminal without polluting the pipe. Emits a `finding_fix_copied` telemetry event. | ||
| - Interactive fix-wizard (`vertaa audit … --interactive`) gains a "Copy fix to stdout" menu choice. Selecting it copies the current finding's recommended fix and stays on the same finding so you can also baseline or accept after copying. |
6 tasks
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.
Summary
package.jsonto0.8.0-alpha.2(skipping the briefly-published0.8.0-alpha.1).[0.8.0-alpha.2](post-publish bug fix) and[0.8.0-alpha.1](Phase 147 CLI Package Isolation feature set).Context
@vertaaux/cli@0.8.0-alpha.1was published earlier today on thenexttag, then immediately superseded by0.8.0-alpha.2after three latent issues surfaced post-publish:vertaa explain <id> --file out.json --copycould not match findings and the pipe-to-clipboard path silently emitted nothing. The CLI now backfills synthetic stable IDs at save + load (audit-engine retrofit is a separate effort).vertaa explain --file out.jsonpreviously only accepted the bare{ issues: [] }shape. The standard{ data: { issues }, meta }envelope written byvertaa audit --format jsonwas not unwrapped, so users had to manually runjqbefore piping.recommendedFix,wcagReference, etc.) while the canonicalIssuetype declared only snake_case. Both shapes are now first-class on the type.latesttag remains at0.6.2(stable). Only consumers explicitly opting in to@nextsee the alpha track.Test plan
package.jsonreads0.8.0-alpha.2CHANGELOG.mdhas[0.8.0-alpha.2] - 2026-05-25(Fixed) and[0.8.0-alpha.1] - 2026-05-25(Added + Fixed) blocksnpm view @vertaaux/cli@0.8.0-alpha.2 versionreturns0.8.0-alpha.2on the registryvertaa audit URL --format json -o out.json && vertaa explain $(jq -r '.data.issues[0].ruleId' out.json) --file out.json --copy | pbcopy && pbpasteputs ONLY the recommended fix in the clipboard🤖 Generated with Claude Code