📝 Check off the CI publish task
The publish job was already tag-only; the coarse NPM_TOKEN assert is replaced by per-step env gates, so an unset secret now skips only its own step.
This commit is contained in:
1 parent
e90d2549e3
commit
60e416b0fe
1 file changed
+6
-6
+6
-6
@@ -54,9 +54,9 @@ Maintenance:
|
|||||||
✔ Guard the invariant in CI (`Assert the baked tool cache is present`) @done
|
✔ Guard the invariant in CI (`Assert the baked tool cache is present`) @done
|
||||||
☐ Enable force-pull for the runner so a changed act-ci image is never missed @low
|
☐ Enable force-pull for the runner so a changed act-ci image is never missed @low
|
||||||
→ the tag encodes only the Node version, so a Dockerfile change yields new content under an unchanged tag; with `forcePull=false` the runner keeps the old image (see CONTRIBUTING § CI runner image)
|
→ the tag encodes only the Node version, so a Dockerfile change yields new content under an unchanged tag; with `forcePull=false` the runner keeps the old image (see CONTRIBUTING § CI runner image)
|
||||||
☐ Improve CI publish
|
✔ Improve CI publish @done
|
||||||
☐ Check whether publish job is only run on tags, if not, guard it
|
✔ Check whether publish job is only run on tags, if not, guard it @done
|
||||||
☐ Gate only single steps
|
✔ Gate only single steps @done
|
||||||
☐ Do not publish to npm, if NPM_TOKEN is not set (e.g. PRs from forks)
|
✔ 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)
|
✔ Do not publish to Gitea, if GITEA_TOKEN is not set (e.g. PRs from forks) @done
|
||||||
☐ Otherwise run the steps
|
✔ Otherwise run the steps @done
|
||||||
Reference in new issue
Block a user