[1stANUNNAKI]

Summary

This PR resolves multiple CI/CD, deployment, and release workflow failures currently affecting main builds, VS Code/JetBrains extension releases, and @continuedev/* npm package publishing:

1. Fix Main Branch Build Artifact Republishing (.github/workflows/main-build.yaml)

• Problem: Every run on main (e.g., runs 29800025075, 29797825835) fails in Find PR workflow run (exit code 1) because gh run list queries --workflow="pr_checks.yaml" (with an underscore) whereas the workflow file is .github/workflows/pr-checks.yaml (with a hyphen). Additionally, pr-checks.yaml only builds vscode-extension-build-Linux (not macOS), and workflow_dispatch's inputs.test_pr_number was ignored.
• Fix: Correct --workflow="pr-checks.yaml", honor inputs.test_pr_number when provided, and scope the republish matrix to [Linux].

2. Fix VS Code Extension Release & Pre-release Deployment (.github/workflows/main.yaml, .github/workflows/preview.yaml)

• Problem:
  • check_release_name hardcoded v1.2.*-vscode in main.yaml and v1.3.*-vscode in preview.yaml, causing v2.0.0-vscode and v2.1.0-vscode release events to skip building and publishing.
  • In both workflows, the release job declares permissions: contents: write on GITHUB_TOKEN but passed secrets.CI_GITHUB_TOKEN to softprops/action-gh-release@v2, failing with HttpError: Resource not accessible by personal access token (runs 27797663453, 27797662635).
  • In preview.yaml, the publish job checked out a detached release tag and ran git checkout -b before invoking peter-evans/create-pull-request@v8 with CI_GITHUB_TOKEN, failing with /usr/bin/git failed with exit code 128.
• Fix: Match any v*.*.*-vscode tag with even minor version in main.yaml and odd minor version in preview.yaml, guard tag checkout when triggered via workflow_dispatch, fetch origin/main before bumping the version in preview.yaml, and use the job-scoped secrets.GITHUB_TOKEN.

3. Fix @continuedev/* Package Releases (.github/workflows/reusable-release.yml)

• Problem: @continuedev/config-yaml, @continuedev/fetch, @continuedev/llm-info, and @continuedev/openai-adapters use semantic-release@^24.2.7 and @semantic-release/npm@^13.1.5, which require Node.js ^22.14.0 || >= 24.10.0. Running npx semantic-release under Node 20 (from .nvmrc) causes the Release step to fail (runs 23666385675, 24546138990, 23881659456).
• Fix: Add a Setup Node.js 24 for semantic-release step before npx semantic-release (matching the pattern used in stable-release.yml).

4. Fix CLI Stable Release Tagging & Token Fallback (.github/workflows/stable-release.yml)

• Problem: Create release on GitHub failed with exit code 128 (run 27790830288) when SEMANTIC_RELEASE_TOKEN was unavailable or the tag already existed.
• Fix: Fall back to secrets.SEMANTIC_RELEASE_GITHUB_TOKEN || secrets.GITHUB_TOKEN (using the workflow's contents: write permission) and force-update the tag (git tag -f) before pushing.

5. Fix JetBrains CI FFmpeg Setup & Release Matrix (.github/actions/run-jetbrains-tests/action.yml, .github/workflows/jetbrains-release.yaml)

• Problem:
  • AnimMouse/setup-ffmpeg@v1 with version: 7.1 fails on ubuntu-latest when uncached (xz: (stdin): File format not recognized / tar: Error is not recoverable: exiting now, exit code 2), blocking jetbrains-tests and require-all-checks-to-pass on PRs.
  • jetbrains-release.yaml referenced the retired macos-12 runner image, hardcoded v1.0.*-jetbrains, and passed an empty ref on workflow_dispatch.
• Fix: Install ffmpeg via apt-get on Ubuntu runners in run-jetbrains-tests, update macos-12 to macos-15-intel, support v*.*.*-jetbrains tags, and fall back to github.ref_name on workflow_dispatch.

6. Fix Issue Auto-Assignment Token Scope (.github/workflows/auto-assign-issue.yaml)

• Problem: pozil/auto-assign-issue@v2 failed on every new issue (HttpError: Resource not accessible by personal access token) because it used secrets.CI_GITHUB_TOKEN instead of secrets.GITHUB_TOKEN (which has permissions: issues: write in the job).
• Fix: Use secrets.GITHUB_TOKEN.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[1stANUNNAKI]

I have read the CLA Document and I hereby sign the CLA

[1stANUNNAKI]

Update: JetBrains CI & Flaky Test Stabilization

Pushed two additional commits to stabilize jetbrains-tests and prevent CI blockage:

1. Autocomplete.kt Integration Test Hardening (e7615b0):

   • Added initial wait (5s) to allow IDE indexing and background workers to settle upon opening Main.java.
   • Replaced fixed single wait(2.seconds) -> tab() with a resilient retry loop (up to 10 iterations) to reliably await the inline LLM ghost text before accepting via Tab on constrained CI runners.

2. Action Fallback Retry (b4370f8):

   • Added automatic rerun for testIntegration --rerun-tasks in .github/actions/run-jetbrains-tests/action.yml to guarantee resilience against transient Xvfb/display latency.

All release, deploy, Node 24, and FFmpeg fixes remain in place.