[ci] use release-drafter bot again (#346)

Author: jameslamb

.github/release-drafter.yml

@@ -0,0 +1,21 @@
+---
+name-template: 'v$NEXT_PATCH_VERSION'
+tag-template: 'v$NEXT_PATCH_VERSION'
+categories:
+  - title: '💡 New Features'
+    label: 'enhancement'
+  - title: '😬 Breaking'
+    label: 'breaking'
+  - title: '🙈 Bug Fixes'
+    label: 'fix'
+  - title: '📖 Documentation'
+    label: 'doc'
+  - title: '🛠 Maintenance'
+    label: 'maintenance'
+change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
+template: |
+  ## Changes
+  $CHANGES
+
+  ## Contributors
+  $CONTRIBUTORS

.github/release.yml

@@ -0,0 +1,22 @@
+---
+name: release-drafter
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: read
+
+jobs:
+  update_release_draft:
+    permissions:
+      contents: write
+    runs-on: ubuntu-latest
+    steps:
+      - uses: release-drafter/release-drafter@b1476f6e6eb133afa41ed8589daba6dc69b4d3f5 # v6.1.0
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          disable-autolabeler: true

.github/workflows/release-drafter.yml

@@ -21,8 +21,7 @@ bin/create-release-pr '0.11.0'
 
 2. Merge that PR.
 3. navigate to https://github.com/jameslamb/pydistcheck/releases
-4. create a draft release
-    - click "generate release notes"
+4. edit the draft release there
     - remove any changelog items that are just "changed the version number" PRs
     - ensure that the tag that'll be created matches the version number, in the form `v{major}.{minor}.{patch}`
 5. click "publish"