Add automated release workflow#21
Merged
Merged
Conversation
No manual version bumping needed — just push a tag like v1.1.0 and the workflow patches manifest.json and package.json, builds, tests, and creates a GitHub Release with the extension zip attached.
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.
Summary
release.ymlGitHub Actions workflow that automatically creates a GitHub Release when a version tag (v*) is pushedmanifest.jsonandpackage.jsonautomatically — no manual version bumping neededRelease flow
git tag v1.1.0 && git push origin v1.1.0That's it. The workflow will:
1.1.0from the tagpackage.jsonandmanifest.json