mirror of
https://github.com/J3vb/OwnCord.git
synced 2026-09-03 03:50:00 +03:00
J3vbandClaude Opus 5
e58df6802e
`gh release create --notes-file CHANGELOG.md` hands GitHub the entire file. v1.2.0-alpha.4 shipped with all 795 lines as its description: every past release back to alpha.1, plus the "How to write an entry" style guide, which is addressed to contributors and has no business on a download page. A reader looking for what changed had to scroll past three prior releases to find it. Slice the section for the tag being published instead, and rewrite its relative `docs/` links to absolute ones — they resolve against the repository, so on a release page they 404 for every reader. Fail closed when the section is missing. A published release with an empty description has already been fetched by the time anyone notices; a failed run can be re-run once the entry is written. Also drop the `changelogen --output CHANGELOG.md` step and the `npm ci` that fed it. It ran after the tag existed, so its from-tag and to-tag were the same commit: it appended an empty `## <tag>...<tag>` heading whose compare link pointed at itself. Nothing else consumed its output. `npm run changelog` still exists for drafting an entry locally, before tagging, which is where generating one is actually useful. Verified against the committed CHANGELOG.md: alpha.4 yields the 73-line curated section (3115 bytes, down from 49775), alpha.1 matches through its titled heading, a bare `v1.2.0` correctly matches nothing rather than swallowing alpha.4, and a missing section exits 1. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>