Merge pull request #27 from umage-ai/feature/release-notes-from-md

Source release notes from RELEASE-NOTES.md

Author: martin-ottosen

.github/workflows/publish.yml

@@ -32,14 +32,27 @@ jobs:
         id: version
         run: echo "VERSION=${GITHUB_REF_NAME#v}" >> $GITHUB_OUTPUT
 
-      - name: Generate release notes from merged PRs
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - name: Resolve release notes
         run: |
-          gh api repos/${{ github.repository }}/releases/generate-notes \
-            -f tag_name=${{ github.ref_name }} \
-            -f target_commitish=${{ github.sha }} \
-            --jq .body > release-notes.md
+          # Carve out the section in RELEASE-NOTES.md whose heading matches
+          # this tag (e.g. "## v0.1.0"). The section runs until the next
+          # "## " heading or EOF. The release fails if no matching section
+          # is found — the curated body is the source of truth for the
+          # GitHub release and the .nupkg's PackageReleaseNotes, so we'd
+          # rather block the publish than silently ship without it.
+          awk -v ver="${GITHUB_REF_NAME}" '
+            $0 ~ "^## " ver "([[:space:]]|$)" { in_section = 1; next }
+            in_section && /^## / { exit }
+            in_section { print }
+          ' RELEASE-NOTES.md > release-notes.md
+
+          if ! grep -q '[^[:space:]]' release-notes.md; then
+            echo "::error file=RELEASE-NOTES.md::No '## ${GITHUB_REF_NAME}' section found in RELEASE-NOTES.md."
+            echo "Add the section, commit, delete + recreate the tag at the new commit, then re-push."
+            exit 1
+          fi
+
+          echo "Using curated '## ${GITHUB_REF_NAME}' section from RELEASE-NOTES.md."
           echo "::group::Release notes"
           cat release-notes.md
           echo "::endgroup::"

CLAUDE.md

@@ -61,10 +61,16 @@ is unused for static file serving.
   confirm first.)
 - Pre-release local verification: `dotnet test` (no `--no-build` — that flag silently uses
   stale test DLLs and can miss compile errors introduced by signature changes).
-- `RELEASE-NOTES.md` at the repo root is a hand-curated, human-readable changelog. Update it
-  in the same PR that introduces user-visible changes. The workflow's auto-generated notes
-  (from PR titles between tags) handle the GitHub release body and `.nupkg`
-  `PackageReleaseNotes` field separately — `RELEASE-NOTES.md` itself is not read by CI.
+- `RELEASE-NOTES.md` at the repo root is a hand-curated, human-readable changelog and is
+  **the source of truth for the release body and the `.nupkg` `PackageReleaseNotes`
+  field**. The publish workflow carves out the `## v<version>` section matching the
+  pushed tag and uses it verbatim. **No matching section → the workflow fails before
+  build**, so the nupkg never ships without a curated body. Update `RELEASE-NOTES.md`
+  in the same PR that introduces user-visible changes.
+- **Before tagging a release, verify `RELEASE-NOTES.md` has an up-to-date
+  `## v<next-version>` section** covering everything merged since the previous tag.
+  If you skip this and CI fails on the tag, the recovery is: add the section, commit,
+  delete + recreate the tag at the new commit, re-push.
 
 ## Key Patterns (inherited from EditorPowertools framework)