chore(release): 0.5.0 — dependency security remediation#10
Merged
Conversation
The committed lockfile shipped vulnerable transitive/runtime deps (axios, qs, follow-redirects + dev-only ajv/brace-expansion/diff/esbuild), and the lockfile had drifted below package.json's declared ranges. - bump axios ^1.13.5 -> ^1.18.0 (direct dep) - overrides: qs ^6.15.2, axios ^1.18.0, follow-redirects ^1.16.0, esbuild ^0.28.1 - npm audit fix for dev-only ajv/brace-expansion/diff - resync package-lock.json `npm audit` now reports 0 vulnerabilities (full tree and --omit=dev). Build, lint, and 93 unit tests all pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Minor bump for the new `qc vrt --config <path>` flag plus the dependency security remediation. Publishing is triggered by pushing the v0.5.0 tag after merge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Cuts the 0.5.0 release: the
qc vrt --config <path>flag (already onmain) + a dependency security pass.Dependency remediation
The committed lockfile had drifted below
package.json's declared ranges and shipped vulnerable deps.npm auditwent from 10 vulnerabilities (3 high, 6 moderate, 1 low) → 0.^1.13.5→^1.18.0(direct dep; was locked at 1.13.2/1.13.3)qs ^6.15.2,axios ^1.18.0,follow-redirects ^1.16.0,esbuild ^0.28.1npm audit fixfor dev-onlyajv/brace-expansion/diffpackage-lock.jsonresyncednpm auditandnpm audit --omit=devboth report 0 vulnerabilities.Version
0.4.3→0.5.0(minor — new backward-compatible--configfeature).Verification
npm run build— cleannpm run lint— 0 errors (pre-existingno-explicit-anywarnings only)npm run test:unit— 93/93 passPublishing
On merge, push the
v0.5.0tag (or draft a GitHub Release for it) to triggerpublish.yml→npm publish --access publicvia OIDC.🤖 Generated with Claude Code