[cd] Move release un-draft to a follow-up job (#100571)
Follow-up to #100121. `publishRelease` no longer mints an App token at
all.
Un-drafting the GitHub release must stay authenticated as the release
App: events caused by `GITHUB_TOKEN` do not trigger workflow runs, and
release-published automations depend on the event. Previously that meant
the bot key had to be available to the `publishRelease` job. With this
change a small `undraftRelease` job runs in `bot-autonomous` instead,
after the gated publish succeeded (the tag is already trusted at that
point), so the key never leaves the two `bot-*` environments.
Backports: #100572 (`releases/lts/active`), #100573
(`releases/lts/maintenance`) — their publish scripts read `lerna.json`,
so the script is adapted there.
---------
Co-authored-by:
Claude Code <noreply@anthropic.com>
Showing
scripts/undraft-release.js
0 → 100644
Please
register
or
sign in
to comment