Add release workflow #7
Merged
Conversation
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
Member
Can it publish on new tags only? I don't suppose we'd always want each commit to be published and failing CI will look confusing. |
Contributor
Author
fixed, we should create a 1.0.0 tag to keep it consistent. |
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.
The new workflow will try to release a fresh version of a package to marketplaces on every commit to master.
Package versions still must be bumped manually. The workflow will fail otherwise since the version published to the marketplace must be unique.
@MartinKolarik two repository secrets must be set:
OVSX_TOKEN- access token for Open VSXVSCE_TOKEN- access token for VS Code Marketplaceresolve #4