This issue tracks the work to design and implement a new batch release process for high-traffic packages in the flutter/packages repository.

For high-traffic packages, requiring every pull request to manually update CHANGELOG.md and pubspec.yaml creates a constant stream of merge conflicts. This slows down contributions and increases the maintenance burden.

The objective is to create a process that eliminates these merge conflicts by batching version and changelog updates. This will likely involve a rolling cron job in cocoon where changelog entries are generated automatically from pull request titles, labels, or specific sections in the PR body.

Motivated by

• ☂️ Move the material and cupertino packages outside of Flutter #101479

We should implement this using go_router and go_router_builder as canaries, since they regularly experience this pain point.