Reproduction
Recorded in commit 0e9930bad03eda97751c49e93b0078aaef51059a:
The health check probed an artifact the supported installation does not have
cli-runtime ran dist/cli.js --version. A git clone — the documented
distribution (ADR-0011) — ships dist/commitlore.mjs and no node_modules, so
dist/cli.js is a file that exists and cannot run. The check therefore reported
fail on the one installation it was written to protect, and doctor exits
non-zero on a fail, so the CI step that clones and runs doctor went red at
f85101a and stayed red for three commits.
I did not notice because I ran the local suite and never looked at CI. The suite
passed at every one of those commits.
The check now probes the bundle first and falls back to the tsc output, so it
follows the artifact the installation actually uses instead of the one a
development checkout happens to have.
Reproduction
Recorded in commit 0e9930bad03eda97751c49e93b0078aaef51059a:
The health check probed an artifact the supported installation does not have
cli-runtimerandist/cli.js --version. A git clone — the documenteddistribution (ADR-0011) — ships
dist/commitlore.mjsand nonode_modules, sodist/cli.jsis a file that exists and cannot run. The check therefore reportedfailon the one installation it was written to protect, anddoctorexitsnon-zero on a
fail, so the CI step that clones and runs doctor went red atf85101a and stayed red for three commits.
I did not notice because I ran the local suite and never looked at CI. The suite
passed at every one of those commits.
The check now probes the bundle first and falls back to the tsc output, so it
follows the artifact the installation actually uses instead of the one a
development checkout happens to have.