feat: add GitHub workflow for vscode pre-release

[tingwai]

Summary by cubic

Adds a GitHub Actions workflow to automate VSCode extension pre-releases. It bumps the extension version, opens an auto-merge PR, tags the release, and publishes a GitHub pre-release with generated notes.

• New Features
  • Manual dispatch with inputs for main commit SHA and pre-release version (auto-increments patch if omitted).
  • Updates extensions/vscode/package.json, creates a prerelease branch, pushes, and opens a PR via gh with auto-merge.
  • Creates tag v{version}-vscode and a GitHub pre-release targeting main with generated release notes between tags.

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[github-actions]

✅ Review Complete

Code Review Summary

⚠️ Continue configuration error. Please verify that the assistant exists in Continue Hub.

---

[tingwai]

@tomasz-stefaniak Adding you as reviewer to see if this is what you had in mind for the pre-release workflow. I left out the previous_version input because that can be detected from the package.json, let me know if you still want that in

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name=".github/workflows/vscode-prerelease.yml">

<violation number="1" location=".github/workflows/vscode-prerelease.yml:161">
If the PR still isn’t merged after the timeout this step only prints a warning, so the workflow proceeds to tag and release code that never landed in main. Make the job fail here to prevent publishing from the wrong commit.</violation>
</file>

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}

[RomneyDa]

Code looks good to me.