tcyeee ed6954a22b ci: publish releases directly instead of leaving them as drafts ... gh release create --draft has been requiring a manual "Publish release" click on GitHub after every CI run since this workflow was added; if that step gets forgotten, Obsidian's manifest.json version has no matching public release ("No release matches your manifest version"). Every prior release was published this way by hand. Drop --draft so a green CI run is itself the publish step, and pull release notes from the pushed annotated tag's message (with --generate-notes as a fallback for lightweight tags) instead of leaving the release body empty. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-07-09 21:25:23 +08:00
..
workflows	ci: publish releases directly instead of leaving them as drafts	2026-07-09 21:25:23 +08:00