A fix release cut the same day as 1.0.0, because 1.0.0 shipped a workflow
that fails on checkout.
Fixed
If you took the v1.0.0 source tarball, its
testsworkflow fails
immediately. Cloningmainwas always fine; only the tagged snapshot is
affected. Nothing about the scraper itself is different — the parser, the
engines and the output are byte-identical between the two tags.
.github/workflows/tests.ymlcarried its own inlined copies of two
checks that also exist in.github/ci_checks.py. The sample-output copy
still importedPlayerandTransfer, the row classes this repo replaced
with a singleProductbefore its first release, so the workflow failed on
a schema that is correct. Both steps now call the shipped checker — which
also widens the--helpcheck from seven entry points to eight — and no
python heredocs remain in that workflow.
Added
- The README now records the canary's first live run: a bare GitHub Actions
runner, a freshly installed Playwright Chromium and no secret configured
scraped/us/makeup/lips/and reported 16 rows, 16 priced,
status=complete, with every canary assertion passing. That is a third
independent address behind the "the paid path is not required" claim,
alongside a residentialcurland the same connection through a real
browser.