Skip to content

Commit 9ddbec5

Browse files
cliffhallclaude
andcommitted
ci: rename the workflow to CI, and fix a README line this PR made stale
The old name — "Run install, format, lint, build, and test on every push" — enumerated steps rather than naming the workflow, and was wrong in two directions: it never mentioned the coverage gate, and "on every push" reads past the two release-gated publish jobs. `CI` renders as `CI / build` and `CI / coverage` in the checks list, where the job name already carries the detail. Display-only: nothing references the name (no badge, no `workflow_run`, no sibling workflow), and branch protection keys off JOB names, which are unchanged. Also: README described the publish jobs as `needs: build`, which the previous commit falsified. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0177mPHAdECD18nLLCTwR5rh Signed-off-by: cliffhall <cliff@futurescale.com>
1 parent 9cd0659 commit 9ddbec5

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

‎.github/workflows/main.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
name: Run install, format, lint, build, and test on every push
1+
name: CI
22

33
on:
44
push:

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -547,7 +547,7 @@ The `smoke:*` scripts run against the in-repo build tree, which is **not** the p
547547

548548
### Cutting a release
549549

550-
Publishing is automated by two release-gated jobs in [`.github/workflows/main.yml`](.github/workflows/main.yml) (`github.event_name == 'release'`, both `needs: build`):
550+
Publishing is automated by two release-gated jobs in [`.github/workflows/main.yml`](.github/workflows/main.yml) (`github.event_name == 'release'`, both `needs: [build, coverage]` — so a release cannot publish with either the build job or the coverage gate red):
551551

552552
- **`publish`** — the npm package. Runs `npm run pack:verify` as the pre-publish gate, asserts the release tag matches the root `package.json` version, then `npm publish --access public --provenance` — a single `npm publish` (v2 is not an npm workspace, so there is no v1-style `publish-all`/`--workspaces`), with a signed provenance attestation via GitHub OIDC (`id-token: write`, `environment: release`, `NPM_TOKEN`).
553553
- **`publish-github-container-registry`** — the container image (see [Docker](#docker)).

0 commit comments

Comments
 (0)