Repository navigation
ci: create a release with generated notes when a version tag is pushed - #6
Merged
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
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.
Adds
.github/workflows/release.yaml. Pushing av*tag:versionin both plugin manifests and both marketplaces, and fails with the mismatched file otherwise.gh release create <tag> --verify-tag --generate-noteswith a fixed install header prepended, so the notes list the merged PRs since the previous tag.Smoke test
git tag v0.2.0 && git push origin v0.2.0) → the Release workflow passes and a GitHub release appears with the install header followed by "What's Changed" and a Full Changelog link.v9.9.9) → the workflow fails at "Check versions" namingplugin.json, and no release is created.