fix(vscode-extension): bump version to 1.13.0

[ajitpratap0]

Summary

• Bumps `vscode-extension/package.json` version from `1.12.1` → `1.13.0`
• Bumps `vscode-extension/package-lock.json` version fields (`1.12.1` → `1.13.0`, and stale `1.10.1` → `1.13.0`)
• Fixes `aquasecurity/trivy-action@0.28.0` → `v0.35.0` (0.28.0 was removed upstream, breaking all PR security scans)

Why

Flagged by the claude-review bot in PR #421:

VSCode extension files still reference v1.12.1

This was missed from the v1.13.0 release plan. Also took the opportunity to fix the Trivy action version which was causing all PRs to fail CI.

Test plan

• `vscode-extension/package.json` version is `1.13.0`
• `vscode-extension/package-lock.json` version fields are `1.13.0`
• Trivy Config Scan passes
• Trivy Repository Scan passes

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
gosqlx-website	Ready	Preview, Comment	Mar 22, 2026 5:04am

[github-actions]

Claude finished @ajitpratap0's task —— View job

---

PR Review: VSCode Extension Version Bump

Todo List:

• Read and analyze the changed files
• Review package.json version changes
• Review package-lock.json version changes
• Check for consistency and completeness
• Assess potential issues and security concerns
• Provide comprehensive review feedback

Review Feedback

This PR correctly addresses the version bump issue identified by the claude-review bot. The changes are straightforward and appropriate for this maintenance task.

✅ What's Done Correctly

1. package.json version bump (vscode-extension/package.json:5):

   • Correctly updated from "version": "1.12.1" to "version": "1.13.0"
   • Follows semantic versioning conventions

2. package-lock.json consistency:

   • Top-level version updated: "version": "1.13.0" (line 3)
   • Root package entry updated: "version": "1.13.0" (line 9)
   • Both changes maintain consistency between package.json and package-lock.json

3. Stale version fix:

   • The PR description mentions fixing a stale packages[""] entry from 1.10.1 → 1.13.0, which appears to be correctly applied

✅ Code Quality Assessment

• No security concerns: Version bumps in package files pose no security risks
• No performance impact: These are metadata changes only
• Follows best practices: Proper semantic versioning and lock file maintenance
• Clean changes: Minimal, targeted modifications without unnecessary alterations

✅ Completeness Check

The changes appear complete for a version bump:

• ✅ package.json version field updated
• ✅ package-lock.json top-level version updated
• ✅ package-lock.json root package version updated
• ✅ No other version references need updating in these files

📋 Suggestions

1. Test Coverage: Consider adding a simple test or verification step to ensure the VSCode extension can be built and packaged with the new version:

   cd vscode-extension && npm run compile && npm run package

2. Version Verification: The PR's test plan mentions checking for no remaining 1.12.1 references. A quick grep across the repository would be valuable:

   grep -r "1.12.1" . --exclude-dir=node_modules --exclude-dir=.git

✅ Final Assessment

This is a clean, necessary maintenance change that properly addresses the missed version bump from the v1.13.0 release. The changes are minimal, correct, and pose no risks. The PR successfully synchronizes the VSCode extension version with the main project version.

Recommendation: ✅ APPROVE - Ready to merge after optional verification steps.

---

Job Run | Branch: fix/vscode-extension-version-1.13.0

[github-actions]

Claude finished @ajitpratap0's task —— View job

---

PR Review: VSCode Extension Version Bump

Todo List:

• Read and analyze the changed files
• Review package.json version changes
• Review package-lock.json version changes
• Review security.yml changes
• Check for consistency and completeness
• Assess potential issues and security concerns
• Provide comprehensive review feedback

Review Feedback

This PR correctly addresses the version bump issue identified by the claude-review bot. The changes are straightforward and appropriate for this maintenance task.

✅ What's Done Correctly

1. package.json version bump (vscode-extension/package.json:5):

   • Correctly updated from "version": "1.12.1" to "version": "1.13.0"
   • Follows semantic versioning conventions

2. package-lock.json consistency:

   • Top-level version updated: "version": "1.13.0" (line 3)
   • Root package entry updated: "version": "1.13.0" (line 9)
   • Both changes maintain consistency between package.json and package-lock.json

3. Security workflow fix (security.yml:79,121):

   • Fixed trivy-action from @0.28.0 → @v0.35.0
   • The old version (0.28.0) was indeed removed upstream, causing CI failures
   • Both trivy jobs now use the correct available version

4. Stale version fix:

   • The PR description mentions fixing a stale packages[""] entry from 1.10.1 → 1.13.0, which appears to be correctly applied

✅ Code Quality Assessment

• No security concerns: Version bumps in package files pose no security risks
• No performance impact: These are metadata changes only
• Follows best practices: Proper semantic versioning and lock file maintenance
• Clean changes: Minimal, targeted modifications without unnecessary alterations

✅ Completeness Check

The changes appear complete for a version bump:

• ✅ package.json version field updated
• ✅ package-lock.json top-level version updated
• ✅ package-lock.json root package version updated
• ✅ No other version references need updating in these files

📋 Suggestions

1. Remaining References: I found that 1.12.1 still exists in several other files (CHANGELOG.md, documentation, etc.), but these are appropriate historical references that should NOT be changed.

2. Test Coverage: Consider adding a simple test or verification step to ensure the VSCode extension can be built and packaged with the new version:

   cd vscode-extension && npm run compile && npm run package

✅ Final Assessment

This is a clean, necessary maintenance change that properly addresses the missed version bump from the v1.13.0 release. The changes are minimal, correct, and pose no risks. The PR successfully synchronizes the VSCode extension version with the main project version.

Recommendation: ✅ APPROVE - Ready to merge after optional verification steps.

---

Job Run | Branch: fix/vscode-extension-version-1.13.0