What problem does it solve?
Maintainers of SkiaSharp need to keep GitHub release milestones accurate: shipped pull requests and linked issues must map to the correct release, upcoming milestone dates must follow the Chromium schedule, and shipped milestones must be closed with open work rolled forward. Doing this manually is error-prone and tedious.
Core Features & Use Cases
- Assignment Reconciliation: Maps merged pull requests and linked issues to the release where they shipped via reconcile-release-assignments.ps1.
- Milestone Maintenance: Updates upcoming Chromium-derived milestone dates, rolls open work to the next unshipped milestone, and closes shipped milestones via update-release-milestones.ps1.
- Safe Read-Only Preview: Runs both operations without -Push first so maintainers can review changes before applying them remotely.
- Use Case: After shipping SkiaSharp 4.153.0, a maintainer runs the read-only reconciliation, reviews the proposed assignment and milestone changes, then re-runs with -Push to apply them.
Quick Start
Ask the assistant to run a read-only release milestone reconciliation for the shipped SkiaSharp version and review the output before pushing any changes.