changelog-publisher omits required eolDate field — fire 400s on create

[sfreudenthaler]

Discovered during the #36750 backfill (the first live fires of the publisher): the Dotcmsbuilds type requires eolDate ("Planned End of Life Date"), which the tool's payload omitted — every create fails with a 400 validation error, so the maiden release run would have failed the same way. The field wasn't flagged as required by the original field inspection.

Fix: payload now sends eolDate; CLI gains --eol-date, defaulting to released date + 1 year (the convention every current-track entry on the site follows — verified against live entries). Backfill of 26.07.06-3 / 26.07.17-01 / 26.07.21-01 / 26.07.27-01 succeeded with the patch.

Also for the ops runbook, discovered in the same session: the service account additionally needs (a) an explicit entry in the System Workflow Publish action's Who can use list, and (b) type-row View+Edit+Publish on dotCMS Builds (create-path checks structure-level write), beyond the children-row grants.

[github-actions]

PRs linked to this issue

• fix(changelog-publisher): send required eolDate field (create path 400s without it) by @sfreudenthaler

[sfreudenthaler]

Fixed by #36759 (merged 2026-07-27): payload now sends required eolDate (CLI --eol-date, default released date + 1 year); the four-version backfill succeeded with the patch. (PR's Closes: #36758 colon form isn't recognized by GitHub auto-close, hence the manual close.)