ci: update publish script for multi-platform builds

[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

CI:

• Build and publish VSIX packages for Windows, macOS (x64 and arm64), and Linux.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the publish script to build and publish multi-platform VSIX packages.

Sequence diagram for multi-platform build and publish process

sequenceDiagram
    participant Matrix as Build Matrix
    participant Runner as GitHub Runner
    participant Artifacts as Artifacts Storage
    participant VSCode as VS Code Marketplace
    participant GitHub as GitHub Releases

    Matrix->>Runner: Start parallel builds for each platform
    loop For each platform
        Runner->>Runner: Download binaries
        Runner->>Runner: Update version
        Runner->>Runner: Package VSIX
        Runner->>Artifacts: Upload platform-specific VSIX
    end
    Runner->>Artifacts: Download all artifacts
    Runner->>VSCode: Publish all platform VSIXs
    Runner->>GitHub: Create release with all VSIXs

Loading

[FILTERED - Architecture diagrams are low quality] Architecture diagram for multi-platform VSIX build and publish workflow

flowchart TB
    subgraph package[Package VSIX Job Matrix]
        direction TB
        win[Windows x64]-->pkg1[Package VSIX]
        linux[Linux x64]-->pkg2[Package VSIX]
        macx64[macOS x64]-->pkg3[Package VSIX]
        macarm[macOS ARM64]-->pkg4[Package VSIX]
        pkg1 & pkg2 & pkg3 & pkg4 -->|Upload| artifacts[(Artifacts Storage)]
    end

    subgraph publish[Publish Job]
        direction TB
        download[Download Artifacts]-->merge[Merge Artifacts]
        merge-->publish_vsix[Publish to VS Code Marketplace]
        merge-->create_release[Create GitHub Release]
    end

    package-->|Dependencies|publish

Loading

File-Level Changes

Change	Details	Files
Adds multi-platform build support	A matrix strategy is used to build for Windows, macOS (x64 and arm64), and Linux. The VSIX is packaged for each target platform using the --target flag. The packaged VSIX files are renamed to include the version and target platform. The artifacts are uploaded for each platform.	.github/workflows/publish.yml
Publishes multi-platform VSIX packages	The publish job now depends on the package job. All packaged VSIX files are downloaded as artifacts. The vsce publish command is updated to publish all downloaded VSIX files.	.github/workflows/publish.yml
Updates release artifacts	The release now includes all platform-specific VSIX files as artifacts.	.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 - here's some feedback:

Overall Comments:

• Since this PR adds multi-platform builds, consider updating the checklist to verify the VSIX package works on all target platforms (Windows, Linux, Mac x64, Mac ARM64)

Here's what I looked at during the review

• 🟢 Functionality: all looks good
• 🟡 General issues: 1 issue found
• 🟡 Security: 1 issue found
• 🟢 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.}

[brendanator]

Looks good to me

Do you actually have to merge this before testing it? Or can you test it and remove the TODOs before merging?