fix(release): surface breaking changes in notes, correct action tag
Release prep — must land before merging #2904
Two problems found while checking what the releases page will show. Both are fixed here; merge this before #2904, since publish.yml runs from main and #2904's merge is what triggers it.
1. Breaking changes were invisible on the releases page
publish.yml generated release notes as a bare package list plus "See individual package CHANGELOGs for details." — v10.5.0 is exactly that.
For v11 that means the Node 22 baseline, 5 removed compressors and the removed type aliases would appear nowhere on the release, leaving upgraders to go digging.
Now the version's own packages/core/CHANGELOG.md section is prepended above the package list. Verified:
- the
awkextraction against the real## 11.0.0entry — captures the full Major Changes block, stops correctly at the next heading - a missing section degrades cleanly to the previous package-list-only output
publish.ymlstill parses and therunscript survives as one scalar (awkandgh release createboth intact)
2. srod/node-minify@v1 never existed
Every doc told users:
- uses: srod/node-minify@v1
But there is no v1 tag on the repo, and release-action.yml has never run — zero runs in its history. That snippet has been broken for everyone who copied it.
Root cause: release-action.yml derives its major tag from the release tag publish.yml creates, which is the monorepo version (v10.5.0, now v11.0.0). So the action's tag line is v11 — v1 was never reachable.
Updated all 31 references to @v11 across docs/src/content/docs/github-action.md (17), packages/action/README.md (5), AGENTS.md (3), .github/actions/node-minify/README.md (3), and .github/actions/node-minify/action.yml (3).
After the v11.0.0 release publishes, release-action.yml fires on release: published and creates the v11 tag, making the documented snippet work for the first time.
Verification
| Gate | Result |
|---|---|
| build | pass |
| lint / typecheck | pass |
| test | 1047 passed (70 files) |
| removed-compressor guard | pass |
YAML parse (publish.yml, both action.yml) | pass |
Note
packages/action/action.yml still declares using: "node20". Left alone deliberately — it's the GitHub runner runtime, not the npm baseline, and CI only warns that Node 20 actions are force-migrated to Node 24.
Summary by cubic
Release notes now include the version’s core CHANGELOG section, and publishing explicitly dispatches the action release workflow so v11 breaking changes and the srod/node-minify@v11 tag are available to users.
- Falls back to package-only notes when the CHANGELOG section is missing.
- Updates all action examples and deprecation messages from
@v1to@v11. - Uploads the action artifact on dispatched runs and overwrites it safely on repeats.
- Manual dispatches must name an existing, non-draft release tag.
- Limits the 30-second timeout to the slow
minify-htmlerror test; other tests keep the default. - Must land before #2904, which triggers the release from
main.
Summary by CodeRabbit
-
Documentation
- Updated GitHub Action usage examples and migration guidance to reference the current v11 release.
-
Release Improvements
- Improved automated publishing and release-note generation, including the current version’s changelog entry.
- Added validation for manually triggered release tags and support for uploading release artifacts during those runs.
- Enabled replacement of existing release artifacts when necessary.
-
Bug Fixes
- Increased the timeout for a Windows-sensitive minification error test to improve release validation reliability.