Trigger the VS Code extension build on each release - #256
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Each explorbot release now ships the Explorbot VS Code extension.
On
release: published, this workflow sends anexplorbot-releasedispatch to testomatio/testeiya. There,vscode-release.ymlbuilds the extension at this release's version, attachesexplorbot-<version>.vsixto the release and publishes it to the VS Code Marketplace and Open VSX. Prereleases get the vsix but skip the marketplaces.prima-*andmdq-*releases are skipped.Before merging
TESTEIYA_DISPATCH_TOKENrepository secret: a fine-grained PAT on testomatio/testeiya with Contents: Read and write.🤖 Generated with Claude Code