ranade-oss makes release checks less owner-dependent
Trusted contributors can now keep the release record current without waiting for a repository owner.
Changes to governed material can refresh the release record automatically, but only after the full verification gate has passed. The update then lands on the pull-request branch and triggers a fresh authoritative check at the new branch head.
- Trusted same-repository contributors can get the generated release record refreshed as part of their pull request.
- Repository owners still have a manual route for exceptional maintenance.
- Pull requests from forks remain read-only, and untrusted contributors cannot use the write-capable route.
That is a sensible trade: less routine release-admin work, with the final check still happening after the automated update.
So what Teams maintaining controlled legal products should care if release evidence is a recurring bottleneck but repository write access needs tight boundaries.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?