Skip to content

v0.1.1 — fixture hygiene

Choose a tag to compare

@jehrr jehrr released this 08 Sep 22:08
· 21 commits to main since this release
ecd8bea

Nothing changes for a caller. No flag, column, exit code or output shape
moved from v0.1.0. If you are scripting against this, v0.1.1 is a drop-in.

Use this release rather than v0.1.0 — its source archive is the scrubbed
one.

Fixed

  • The fixtures carried session material and one real person's data. A real
    page capture brings the session that fetched it — three anonymous, expired
    sessionId values and their CSRF tokens — and, on a review, a real
    customer's display name, profile permalink, review id, uploaded-photo ids
    and words. All of it is now an obvious placeholder. Everything Amazon
    generates around it (the accessibility filler that is part of the body
    node's text, the date wording, the badges, the markup) is untouched, because
    that is what the checks actually read: the structure of a review, not the
    person.
  • A guard so it does not come back with the next capture. Patterns rather
    than literals, so a new capture's values are caught too, and verified to
    fire rather than only to stay quiet.
  • Both Claude workflows failed instead of skipping without their token,
    putting a permanently red check on every pull request. A check that is
    always red teaches everyone to ignore checks.

244 offline checks (was 239).

Known, and not reachable from here

The pre-scrub values remain in this repository's history — in the v0.1.0 tag
and in PR #1's own refs, which stay attached to that pull request. What that
history holds is three expired anonymous session ids, their dead CSRF tokens,
and one Amazon review that is public on amazon.com today. Removing it entirely
would need a fresh repository, not a commit on top.