ranade-oss makes upstream adaptations prove their paperwork matches
A new safeguard stops approved source changes from passing the build but failing because their governed records are out of date.
When a deliberate adaptation changes governed material, the fork's automated checks now refresh the records that must match it before verification runs. The scope is deliberately narrow: it applies only to intentional staged changes in GitHub Actions, while ordinary pull requests remain read-only.
- Public content records are regenerated.
- Ontario workflow records are regenerated.
- The completion dossier is refreshed.
- The release manifest is updated to describe the actual released material.
Only the named generated records can be added automatically, and the existing clean-tree and container checks remain in place.
So what Legal teams relying on controlled source material should care: this reduces avoidable release failures without weakening the approval trail.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?