ranade-oss makes legal-source release checks less brittle

The fork now distinguishes between a useful source directory being down and the legal sources a release actually depends on.

workflowinfrastructure

Release checks still stop when Ontario e-Laws or Justice Laws cannot be verified. Those remain the hard gate.

  • A2AJ can fail without blocking the release.
  • Both public-facing and official data-service links for Ontario e-Laws are accepted.
  • Temporary web failures get a limited number of retries.
  • A failed check keeps a sanitized record of what each provider reported, and scheduled runs retain that record too.

That leaves a usable audit trail when a rehearsal fails, without weakening checks on the required sources.

So what Legal-ops teams relying on current legal materials should care because the release process is less likely to stall on a secondary outage while still refusing to proceed when core sources cannot be confirmed.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from ranade-oss/ROSS-RanadeOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
9914d166 Fix provider-specific legal-source release gates ranade-oss 2026-08-04 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1062.md from inside the repo you want the changes in.

⬇ Download capture-thread-1062.md