From 53e15084dca56d7d1a44b4b89df1442cbf08a8f9 Mon Sep 17 00:00:00 2001 From: awork Date: Sun, 1 Nov 2026 01:12:15 +0800 Subject: [PATCH] fix(release): direct-path GitHub Release notes always ended up '- initial release' MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Create-GitHub-Release step runs AFTER Create-tag, which tags v$VER locally in the same checkout. Bare 'git describe --tags --abbrev=0' then returns that brand-new local tag, LAST == v$VER -> else-branch -> the placeholder body. Every direct-path release was destined for '- initial release'; release-bugfix.yml (merge-gated path) already carries the guard ("`git describe --match 'v*' --exclude "v$VER*" ...`") — restore the same line here. Proof (v0.1.210, first-ever direct-path publish on 2026-11-01): release body shipped as '- initial release' (17 bytes) vs v0.1.209's proper 20KB changelog; notes since v0.1.209 were back-filled manually. --- .github/workflows/release-manual.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release-manual.yml b/.github/workflows/release-manual.yml index 3f518852cb..60ce898908 100644 --- a/.github/workflows/release-manual.yml +++ b/.github/workflows/release-manual.yml @@ -516,7 +516,7 @@ jobs: GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} run: | VER="${{ steps.version.outputs.version }}" - LAST="$(git describe --tags --abbrev=0 2>/dev/null || echo "")" + LAST="$(git describe --match 'v*' --exclude "v$VER*" --tags --abbrev=0 2>/dev/null || echo "")" NOTES="$RUNNER_TEMP/release-notes.md" if [ -n "$LAST" ] && [ "$LAST" != "v$VER" ]; then {