docs: document release changelog recovery path

.github/workflows/release.yml

@@ -334,6 +334,14 @@ jobs:
         id: version
         run: echo "VERSION=${GITHUB_REF#refs/tags/}" >> "$GITHUB_OUTPUT"
 
+      - name: Build changelog artifacts for release
+        run: |
+          if find changes -maxdepth 1 -name '*.md' -not -name README.md -print -quit | grep -q .; then
+            bun run changelog:build --version "${{ steps.version.outputs.VERSION }}"
+          else
+            echo "No pending changelog fragments found."
+          fi
+
       - name: Verify changelog is ready for tagged release
         run: bun run changelog:check --version "${{ steps.version.outputs.VERSION }}"
 

docs/RELEASING.md

@@ -8,6 +8,7 @@
 4. Bump `package.json` to the release version.
 5. Build release metadata before tagging:
    `bun run changelog:build --version <version> --date <yyyy-mm-dd>`
+   - Release CI now also auto-runs this step when releasing directly from a tag and `changes/*.md` fragments remain.
 6. Review `CHANGELOG.md` and `release/release-notes.md`.
 7. Run release gate locally:
    `bun run changelog:check --version <version>`
@@ -29,6 +30,8 @@ Notes:
 - Pass `--date` explicitly when you want the release stamped with the local cut date; otherwise the generator uses the current ISO date, which can roll over to the next UTC day late at night.
 - `changelog:check` now rejects tag/package version mismatches.
 - `changelog:build` generates `CHANGELOG.md` + `release/release-notes.md` and removes the released `changes/*.md` fragments.
+- In the same way, the release workflow now auto-runs `changelog:build` when it detects unreleased `changes/*.md` on a tag-based run, then verifies and publishes.
 - Do not tag while `changes/*.md` fragments still exist.
+- If you need to repair a published release body (for example, a prior version’s section was omitted), regenerate notes from `CHANGELOG.md` and re-edit the release with `gh release edit --notes-file`.
 - Tagged release workflow now also attempts to update `subminer-bin` on the AUR after GitHub Release publication.
 - Required GitHub Actions secret: `AUR_SSH_PRIVATE_KEY`. Add the matching public key to your AUR account before relying on the automation.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "subminer",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "All-in-one sentence mining overlay with AnkiConnect and dictionary integration",
   "packageManager": "bun@1.3.5",
   "main": "dist/main-entry.js",

src/release-workflow.test.ts

@@ -24,6 +24,11 @@ test('release workflow verifies a committed changelog section before publish', (
   assert.match(releaseWorkflow, /bun run changelog:check/);
 });
 
+test('release workflow builds changelog artifacts when fragments are pending', () => {
+  assert.match(releaseWorkflow, /Build changelog artifacts for release/);
+  assert.match(releaseWorkflow, /changelog:build --version/);
+});
+
 test('release workflow verifies generated config examples before packaging artifacts', () => {
   assert.match(releaseWorkflow, /bun run verify:config-example/);
 });