pirl-unc / mhcgnomes / 33463360103
90%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 41
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 89.198%. Remained the same
33463360103

push

github

web-flow 
Build with the resolved venv, and move the workflows off Node 20 (#151)

* Build with the resolved venv, and move the workflows off Node 20

#101: build_distributions used sys.executable -- whatever launched
deploy.py -- not the venv the script had just resolved and reported. The
3.33.6 release printed "Using venv: .venv" and then built through a
Homebrew Python 3.14 with no build module, after lint and 15,127 tests
had passed. Still live on this machine: sys.executable is a shared
virtualenv while .venv/bin/python is a uv-managed 3.12.6.

Config now carries the interpreter alongside env so the two cannot
drift, resolution is DEPLOY_PYTHON then the venv interpreter then
sys.executable, the availability check finally gets cfg.env, and the
interpreter is printed so a mismatch shows up in the log rather than
when build turns out to be missing.

#94: every actions/* pin moves to the lowest major whose action.yml
declares runs.using: node24 -- checkout v5, setup-python v6,
upload-artifact v6, download-artifact v7, cache v5, configure-pages v6,
deploy-pages v5, upload-pages-artifact v5. Read from each manifest
rather than assumed.

Lowest-that-qualifies rather than latest, deliberately:
download-artifact@v8 makes a hash mismatch a hard error and migrates to
ESM, and both artifact actions run only on tag push and
workflow_dispatch, so PR CI cannot verify them. checkout, setup-python
and cache are exercised by tests.yml and docs.yml on this PR.

Closes #101
Closes #94

Claude-Session: https://claude.ai/code/session_012s4siLj2Vm33eNMGjNSazH

* Do not prefer a venv that cannot build

Code review caught that my first fix would have broken every release.
It always preferred the venv interpreter, but develop.sh installs only
.[dev,docs] and this repo's .venv has neither build nor setuptools nor
wheel, while the launching interpreter has all three. So ./deploy.sh
would have aborted at the availability check, after lint and 15,868
tests -- inverting the failure rath... (continued)

4137 of 4638 relevant lines covered (89.2%)

0.89 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33463360103.1 41
89.2
 GitHub Action Run
Source Files on build 33463360103