📝 Record the automatic-token publish design in the backlog

Point 1 dropped the GITEA_TOKEN gate (the run's automatic github.token is
always present), and point 2 added the all-or-nothing check; keep the checked
task from claiming behavior the workflow no longer has.
This commit is contained in:
tmu committed 2026-09-15 09:25:42 +00:00
1 parent 79b4d8c005
commit f984576d4e
1 file changed
+2 -1
+2 -1
View File
@@ -58,5 +58,6 @@ Maintenance:
✔ Check whether publish job is only run on tags, if not, guard it @done ✔ Check whether publish job is only run on tags, if not, guard it @done
✔ Gate only single steps @done ✔ Gate only single steps @done
✔ Do not publish to npm, if NPM_TOKEN is not set (e.g. PRs from forks) @done ✔ Do not publish to npm, if NPM_TOKEN is not set (e.g. PRs from forks) @done
✔ Do not publish to Gitea, if GITEA_TOKEN is not set (e.g. PRs from forks) @done ✔ Do not publish to Gitea — uses the run's automatic `github.token`, so no secret gate is needed @done
✔ Otherwise run the steps @done ✔ Otherwise run the steps @done
✔ Fail the job unless both the Gitea release and npm publish succeeded @done