You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a conda-owned action that scans recent commits, updates .authors.yml for new contributors and alternate emails, and opens or updates a PR. A check-only mode validates without writing. Rever still handles .mailmap and AUTHORS.md at release time.
Why is this needed?
Stale .authors.yml is a common cause of rever failures during release week. Fixing it mid-release involves painful back-and-forth between .authors.yml and .mailmap. Keeping authors metadata current on main avoids that firefighting.
Add a weekly prepare-authors workflow template to infrastructure sync
Update RELEASE.md and RELEASE_ON_DEMAND.md for continuous authors maintenance and what rever still owns at release
Pilot in conda/conda and conda-build, then roll out to other rever-based repos
Additional Context
Complements #1378. Default: weekly prepare on main, scanning since latest tag. Doc updates should land after or alongside infrastructure#1356 to avoid RELEASE.md conflicts.
What is the idea?
Add a conda-owned action that scans recent commits, updates .authors.yml for new contributors and alternate emails, and opens or updates a PR. A check-only mode validates without writing. Rever still handles .mailmap and AUTHORS.md at release time.
Why is this needed?
Stale .authors.yml is a common cause of rever failures during release week. Fixing it mid-release involves painful back-and-forth between .authors.yml and .mailmap. Keeping authors metadata current on main avoids that firefighting.
What should happen?
Additional Context
Complements #1378. Default: weekly prepare on main, scanning since latest tag. Doc updates should land after or alongside infrastructure#1356 to avoid RELEASE.md conflicts.