chore: Automate extensions publishing

[carole-lavillonniere]

Motivation

This PR automates the publishing process for the LocalStack VS Code extension to both the Visual Studio Marketplace and Open VSX Registry. It introduces an automated workflow that can be triggered manually to publish the extension to both marketplaces, ensuring consistency and reducing manual effort.

The extension is published to both marketplaces by default, but that can be overwritten using the GH CLI with inputs, see example below.

Trigger:

• Via GitHub UI (Actions tab → Select workflow → Re-run all jobs)
• Via GitHub CLI: gh workflow run publish.yml -f publish_vscode_marketplace=true -f publish_ovsx=false --ref branch-name

The version is extracted from branch name (strips leading 'v' if present, since it is the convention so far for branch names) and validates it matches package.json version.

Other changes

Added Makefile targets for lint and test to provide a single source of truth for quality checks.

Testing

The workflows were tested by publishing version 1.2.5 with the --pre-release flag. Contrary to what I initially described in DRG-69, VS Code Marketplace pre-releases cannot have version suffixes (like -beta.1). They use the same version format as regular releases. The test pre-releases (version 1.2.5) are now live in both marketplaces but won't auto-update users unless they opted-in. These cannot be unlisted.

✔️ Successfully tested the pre-release extension in VSCode:

Next release should be version 1.2.6 to supersede the pre-release versions. Will create the release 1.2.6 with a subsequent PR.

[carole-lavillonniere]

towards DRG-69

[skyrpex]

Very nice work!

I'd like to suggest merging publish-ovsx and publish-vs-marketplace into a single workflow so both are triggered with one action rather than running them separately, unless there's a specific reason not to do so.

In the future, we might want to automate publishing further, e.g. deducing the next version semantically.

[carole-lavillonniere]

Very nice work!

I'd like to suggest merging publish-ovsx and publish-vs-marketplace into a single workflow so both are triggered with one action rather than running them separately, unless there's a specific reason not to do so.

In the future, we might want to automate publishing further, e.g. deducing the next version semantically.

Yes that's better. We now have one workflow that publishes to both marketplaces by default 1d2c4bb
The behavior can be changed by using inputs and the GH CLI gh workflow run publish.yml -f publish_vscode_marketplace=true -f publish_ovsx=false --ref branch-name
Updated the PR description.

Agreed it can be automated further, some points are also mentioned in the ticket https://linear.app/localstack/issue/DRG-69/automate-publishing-to-vs-marketplace-and-open-vsx

[skyrpex]

Looking great 👍🏻