ranade-oss makes its legal-source release gate less brittle

Optional-source hiccups should no longer hold up a release, while the core Canadian legal sources remain protected.

workflowinfrastructure

ranade-oss has tightened the checks that run before its public releases, fixing a flaw that treated every legal source as equally essential. Ontario e-Laws and Justice Canada still have to be available; A2AJ coverage can now be temporarily unavailable without stopping the release.

The update also adds sensible retries for short-lived failures, corrects a false rejection of valid Ontario responses, and fixes an edge case affecting a first deployment. The result is a release process that is less likely to be derailed by a momentary service problem without becoming casual about the sources users depend on.

So what Legal teams relying on current Canadian primary-law material should care because this makes updates more dependable while keeping the important source checks intact.

View this fork on GitHub →

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

Commits in this thread

3 commits 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
721e10c0 Fix provider-specific legal-source release gates (#76) ranade-oss 2026-08-04 ↗ GitHub
Merge PR #76 after exact-head Baseline verification
7f427c4b Fix fresh legal-source release gate (#86) 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-905.md from inside the repo you want the changes in.

⬇ Download capture-thread-905.md