mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-05 03:27:07 +09:00
Myasnikov Daniil
6fe15b0bf5
release-1.6 was cut at v1.6.0 on 2026-07-22, and the finalize fixes landed on main afterwards, so shipping v1.6.1 from this line would repeat two defects v1.6.0 hit. Workflows run from the ref they fire on: a promote PR based on release-1.6 runs THIS file, not main's. Carries three upstream commits, after which this file is byte-identical to main, so future backports touching it will not conflict:01e1e7188persist-credentials: false on the checkoutf49d54a68publish the release with the merged changelog as its bodyba67fea7ddrop paths-ignore from the trigger Without the first, the checkout persists GITHUB_TOKEN as an http.extraheader that silently wins over the app token injected by git remote set-url. The stable tag then pushes as GITHUB_TOKEN, which creates no workflow run, so tags.yaml never fires and its generate-changelog and update-website-docs backstops stay silent. That is exactly what happened to v1.6.0. Without the second, the release publishes with the draft's body ("Promoted from vX.Y.Z-rc.N"). The two compound on a maintenance line: a patch's changelog is committed to release-1.6 and never reaches main, and update-releasenotes.yaml only watches main, so nothing would ever sync it. v1.6.1 would ship with placeholder release notes permanently. The third is latent rather than active — a promote PR carrying only docs/changelogs/vX.Y.Z.md would be dropped by the filter, producing no finalize run, no tag and no error. v1.6.1 will carry tag-string rewrites so it would not have fired, but the filter has no remaining purpose now that the promote PR always carries a changelog. actionlint and zizmor clean; no bats suite references this workflow, and hack/promote-gate-contract.bats does not exist on this line. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>