ci: the publish workflow needs the browser test environment too #73

Merged

mph merged 1 commit from ci/publish-needs-the-browser-env into main

2026-09-05 19:26:49 +00:00

mph commented

2026-09-05 19:10:17 +00:00

Owner

publish.yml gates on ./mill __.test, which includes ui.js.test — the element tested in a real
DOM. jsdom comes from package.json, and this workflow never installed it, so the module could not
start and the gate below it was never reached.

ci.yml:173-181 has carried the two steps since that module landed, with a comment saying why.
publish.yml did not, and nothing noticed because no release has been cut since.

Found by cutting one. Both runs failed at the test step: the merge to main (run 1929) and
v0.6.0 itself (run 1930). The registry answers 404 for
works/iterative/claude-code-query-core_3/0.6.0 — the tag published nothing.

Recovering the release

A tag's run uses the workflow file from the tagged commit, so re-running 1930 would use the broken
one. After this merges, v0.6.0 has to be moved onto a commit that contains the fix. That is safe
here for the one reason that makes it safe anywhere: nothing was published, so there is nothing to
overwrite — the registry refuses to overwrite a release, and this is the only window in which the
tag can be moved at all.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XTrxcxBQiNjXh79dN8Sh5x

`publish.yml` gates on `./mill __.test`, which includes `ui.js.test` — the element tested in a real DOM. jsdom comes from `package.json`, and this workflow never installed it, so the module could not start and the gate below it was never reached. `ci.yml:173-181` has carried the two steps since that module landed, with a comment saying why. `publish.yml` did not, and nothing noticed because no release has been cut since. **Found by cutting one.** Both runs failed at the test step: the merge to `main` (run 1929) and `v0.6.0` itself (run 1930). The registry answers 404 for `works/iterative/claude-code-query-core_3/0.6.0` — the tag published nothing. ## Recovering the release A tag's run uses the workflow file from the tagged commit, so re-running 1930 would use the broken one. After this merges, `v0.6.0` has to be moved onto a commit that contains the fix. That is safe here for the one reason that makes it safe anywhere: nothing was published, so there is nothing to overwrite — the registry refuses to overwrite a release, and this is the only window in which the tag can be moved at all. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01XTrxcxBQiNjXh79dN8Sh5x

mph added 1 commit

2026-09-05 19:10:17 +00:00

ci: the publish workflow needs the browser test environment too

CI / Check Formatting (pull_request) Successful in 52s

Details

CI / Compile (pull_request) Successful in 1m16s

Details

CI / Check Linting (pull_request) Successful in 56s

Details

CI / Run Tests (pull_request) Successful in 1m27s

Details

CI / Check Bundle Size (pull_request) Successful in 45s

Details

CI / Run Integration Tests (pull_request) Successful in 1m41s

Details

fbf7eaf5da

`publish.yml` gates on `./mill __.test`, which includes `ui.js.test` — the
element tested in a real DOM. jsdom comes from package.json, and this workflow
never installed it, so the module could not start and the gate was never
reached. `ci.yml` has carried the two steps since that module landed; this one
did not, and nothing noticed because no release has been cut since.

Found by cutting one: the run for the merge to main failed here, and so did
the run for v0.6.0 — which means the tag published nothing.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XTrxcxBQiNjXh79dN8Sh5x

mph merged commit 6031a1a606 into main

2026-09-05 19:26:49 +00:00

mph deleted branch ci/publish-needs-the-browser-env

2026-09-05 19:26:49 +00:00

mph referenced this pull request from a commit

2026-09-05 19:26:49 +00:00

Merge pull request 'ci: the publish workflow needs the browser test environment too' (#73) from ci/publish-needs-the-browser-env into main