feat: update back to real releases after testing

[Hellebore]

Checklist

• If package.json or yarn.lock have changed, then test the VSIX built by yarn run vsce package works from a direct install

Summary by Sourcery

Publish full releases of the VS Code extension instead of pre-releases.

CI:

• Publish VS Code extension as a full release.

Deployment:

• Create full releases instead of pre-releases.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the release process to create real releases instead of pre-releases. This was done by removing the --pre-release flag from the vsce package and vsce publish commands, and by setting prerelease: false in the release-action configuration.

[FILTERED - Architecture diagrams are low quality] Architecture diagram showing the release pipeline components

graph LR
    A[GitHub Actions] --> B[VSCode Extension Package]
    B --> C[VSCode Marketplace]
    B --> D[GitHub Release]

    subgraph Release Process
    B
    end

    subgraph Distribution Channels
    C
    D
    end

    note[Note: All components now<br/>publish full releases<br/>instead of pre-releases]
    style note fill:#f9f,stroke:#333,stroke-width:2px

Loading

Flow diagram of the updated release process

graph TD
    A[Start Release Process] --> B[Update Version Number]
    B --> C[Package VSCode Extension]
    C --> D[Rename VSIX File]
    D --> E[Download Artifacts]
    E --> F[Publish to VSCode Marketplace]
    F --> G[Create GitHub Release]
    G --> H[End Release Process]

    style C fill:#90EE90,stroke:#006400
    style F fill:#90EE90,stroke:#006400
    style G fill:#90EE90,stroke:#006400

    note[Note: Green nodes indicate<br/>removal of pre-release flags]
    style note fill:#f9f,stroke:#333,stroke-width:2px

Loading

File-Level Changes

Change	Details	Files
Removed the pre-release flag when packaging the VSIX.	Removed the --pre-release flag from the yarn vsce package command	.github/workflows/publish.yml
Removed the pre-release flag when publishing the VSIX.	Removed the --pre-release flag from the yarn vsce publish command	.github/workflows/publish.yml
Ensured the GitHub release is not marked as a pre-release.	Set prerelease: false in the release action configuration	.github/workflows/publish.yml
Removed TODO comments.	Removed TODO comments related to making the release not a pre-release	.github/workflows/publish.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Hellebore - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 Functionality: all looks good
• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Review instructions: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

LangSmith trace

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}