setup release workflow #2
Merged
Conversation
This file contains 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
Added a GH Actions workflow for including a VSIX file along with published releases
fixed an issue with trigger syntax
- Updated workflow to trigger upon a semantic ver tag push - The release is created by the action now instead of being triggered by it. - Added a step to obtain the release version and determine if it is a pre-release tag. It also checks compatibility with the package.json - Refactored vsix packaging to have the version of the release
sarvalabs-sarthak
approved these changes
Jul 21, 2023
- Added a step to publish to VS Code Marketplace - Added repo checks
bump down the version to v0.0.1 for testing publish
- Added link for the marketplace link and update install instructions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR sets up the release workflow for this VS Code Extension.
package.jsonfile. (must match for a stable release and match the primary version for pre-release tags which must have the structure ofv*.*.*-rc.*)Note: If the Marketplace can be setup within this PR, the README needs to be updated as well