EverOS/.github/workflows
zhanghui d5668dcba1
ci: take the release page's prose from the CHANGELOG too (#391)
Leaving the lead summary and the upgrade notes to be composed at publish
time put the writing at the worst possible moment — weeks after the changes,
with no review. Both belong in the CHANGELOG entry, which the release PR is
already editing.

The lead needed no code: text between the version heading and the first
group already flowed into the page. The Upgrade group did — CI appended its
own `## Upgrade`, so a CHANGELOG that carried upgrade notes produced two
headings. The group is now lifted out and the boilerplate wrapped around it,
pip line above, compare link below, matching every page since 1.1.3.

Publishing is now a read-through and a click.

Co-authored-by: zhanghui <zhanghui@shanda.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-07 11:01:40 +08:00
..
ci.yml ci: enforce the file-size ceiling on pull requests (#387) 2026-08-05 07:57:09 +08:00
commits.yml docs(readme): polish launch highlights and banner (#261) 2026-06-06 19:49:59 +08:00
docs.yml ci(docs): run docs check on every PR so its required check reports 2026-07-24 16:12:59 +08:00
release.yml ci: take the release page's prose from the CHANGELOG too (#391) 2026-08-07 11:01:40 +08:00