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
{{ message }}
Repository navigation
Commit d3dde75
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+13-4Lines changed: 13 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,10 +107,20 @@ Releases are automated with [release-please][release-please]. There is no releas
107
107
- attaches the assets to the release that release-please drafted, and
108
108
- publishes the release (creating the `vX.Y.Z` tag), which redeploys the website and triggers the automatic [Homebrew cask bump][homebrew-cask-autobump-workflow] (workflow runs ~3 hours).
109
109
110
-
4.**(Optional) Update milestones:**
110
+
4.**Milestones and notifications are automated.**
111
111
112
-
- Edit the current [Milestone][github-milestones]: add a link to the release notes, set the due date to the release date, and close it.
113
-
- Create a [New Milestone][github-new-milestone] for the next release cycle.
112
+
- An open [Milestone][github-milestones] titled `Release X.Y.Z` is kept in step with the release-please version, and merged pull requests are attached to it as they land.
113
+
- When the release is published, the milestone is finalized: its description becomes the release URL, its due date is set to the release date, and it is closed.
114
+
- A separate job comments once on every pull request included in the release, linking contributors to the release page. Re-runs are idempotent and never post duplicate comments.
115
+
116
+
No manual milestone creation, renaming, or closing is required.
117
+
118
+
#### Release automation permissions
119
+
120
+
- Packaging and publication use `contents: write`.
0 commit comments