fix: resolve vsce package failure with Yarn 4 Berry

[jonathannorris]

Summary

• Add --no-dependencies flag to vsce package and vsce publish scripts to skip yarn list --prod --json which doesn't exist in Yarn 4 Berry
• Update @vscode/vsce from ^2.20.1 to ^3.7.1

Context

The release workflow fails at the "Package VSCode Extension" step because vsce detects yarn.lock and runs yarn list --prod --json to walk the dependency tree. This command doesn't exist in Yarn 4 — it was a Yarn 1 Classic command.

Since the extension bundles everything via webpack, vsce doesn't need to walk the dependency tree at all. --no-dependencies is the recommended approach for webpack-bundled extensions.

Fixes the failure in https://github.com/DevCycleHQ/vscode-extension/actions/runs/23069857168

[Copilot]

Pull request overview

Fixes the VS Code extension packaging/publishing flow under Yarn 4 Berry by updating vsce usage and its version, avoiding Yarn Classic-only dependency-walking behavior during packaging.

Changes:

• Add --no-dependencies to vsce package / vsce publish scripts.
• Upgrade @vscode/vsce to ^3.7.1 (with corresponding yarn.lock updates).
• Update the release workflow’s version-bump command syntax for Yarn 4.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
package.json	Updates vsce scripts to skip dependency scanning; bumps @vscode/vsce version.
yarn.lock	Lockfile updates resulting from the @vscode/vsce upgrade and dependency graph changes.
.github/workflows/release.yml	Adjusts the version bump step to a Yarn 4-compatible invocation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.