Repository navigation
ci: release by manual dispatch with a version bump - #10
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.
Releases no longer need a hand-edited version bump and a pushed tag. The Release workflow now runs from Actions → Release → Run workflow on
main, with apatch/minor/majorchoice. It:plugin.jsonfiles and bothmarketplace.jsonfiles, then checks each one.chore: release vX.Y.Ztomain, tags it, and pushes both atomically.The tag-push trigger is removed. The workflow now creates the tag itself, and a tag pushed with the workflow token wouldn't start another workflow anyway.
Smoke test
mainwithpatch. Achore: release v0.2.1commit lands onmain, tagv0.2.1exists, and releasev0.2.1lists fix: gallery crash when sorting boolean pinned flags #8 under the install header.main. Each says0.2.1.main. The job is skipped.