chore: remove pre-release CI for extension, too much work and doesn't make sense for us

[Crunchyman-ralph]

What type of PR is this?

• 🐛 Bug fix
• ✨ Feature
• 🔌 Integration
• 📝 Docs
• 🧹 Refactor
• Other:

Description

Related Issues

How to Test This

# Example commands or steps

Expected result:

Contributor Checklist

• Created changeset: npm run changeset
• Tests pass: npm test
• Format check passes: npm run format-check (or npm run format to fix)
• Addressed CodeRabbit comments (if any)
• Linked related issues (if any)
• Manually tested the changes

Changelog Entry

---

For Maintainers

• PR title follows conventional commits
• Target branch correct
• Labels added
• Milestone assigned (if applicable)

Summary by CodeRabbit

• Chores
  • Removed deprecated pre-release script and extension pre-release workflow to streamline CI.
  • Consolidated release candidate publishing to use Changesets directly within the existing pre-release workflow.
  • Cleaned up workflow configuration by removing unused publishing secrets.
  • No user-facing changes or impact to product functionality.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 196e7ef

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Removes the RC-specific script and the extension pre-release workflow, and updates the main pre-release workflow to run “npx changeset publish” directly, dropping marketplace publishing secrets from that step.

Changes

Cohort / File(s)	Summary
RC script removal ./.github/scripts/pre-release.mjs	Deleted Node script that validated RC mode, published via Changesets, and created/pushed git tag extension-rc@.
Extension pre-release workflow removal ./.github/workflows/extension-pre-release.yml	Deleted workflow that built, packaged, and published the VS Code extension as a pre-release to VS Code Marketplace and Open VSX, and uploaded artifacts.
Pre-release workflow update ./.github/workflows/pre-release.yml	Replaced script invocation with “npx changeset publish” and removed VSCE_PAT and OVSX_PAT env secrets from the publish step.

Sequence Diagram(s)

sequenceDiagram
  participant GitHub Actions as pre-release.yml
  participant Changesets as npx changeset publish
  participant npm Registry as npm

  GitHub Actions->>Changesets: Run publish
  Changesets->>npm Registry: Publish packages
  npm Registry-->>Changesets: Publish result
  Changesets-->>GitHub Actions: Exit code/logs

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• chore: implement pre-release for extensions #1097: Introduced the pre-release script/workflow that this PR removes; directly related.
• Release 0.24.0 #1098: Adjusted the same pre-release workflows/scripts later; this PR reverts those paths.
• chore: fix CI checker, improve it #1099: Modified RC pre-release workflow logic; overlaps with the workflow changes here.

Suggested reviewers

• eyaltoledano

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e3ed4d7 and 196e7ef.

📒 Files selected for processing (3)

• .github/scripts/pre-release.mjs (0 hunks)
• .github/workflows/extension-pre-release.yml (0 hunks)
• .github/workflows/pre-release.yml (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/remove.pre.release.ci.for.extension

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.