docs: no more develop branch (#3433)

.github/workflows/docs.yml

@@ -6,7 +6,6 @@ on:
   push:
     branches:
       - main
-      - develop
       - v3.0
 
 jobs:
@@ -44,10 +43,6 @@ jobs:
         run: pdm run python tools/build_docs.py docs-build --version main
         if: github.event_name == 'push' && github.ref == 'refs/heads/main'
 
-      - name: Build docs (develop branch)
-        run: pdm run python tools/build_docs.py docs-build --version develop
-        if: github.event_name == 'push' && github.ref == 'refs/heads/develop'
-
       - name: Build docs (v3.0 branch)
         run: pdm run python tools/build_docs.py docs-build --version 3-dev
         if: github.event_name == 'push' && github.ref == 'refs/heads/v3.0'

.github/workflows/pr-merged.yml

@@ -5,8 +5,8 @@ on:
     types:
       - closed
     branches:
-      - develop
       - main
+      - v3.0
 
 jobs:
   close_and_notify:
@@ -19,6 +19,9 @@ jobs:
           script: |
             const prNumber = context.payload.number
             const branch = context.baseRef
+            # TODO: `develop` no longer exists. Need a new way to determine if the
+            # change will be introduced in a major, minor, or patch release.
+            # possibly conventional commit standards in the PR title or by labels?
             const isDevelop = branch === "develop"
             const commentBody = `<!--closing-comment-->\nThis issue has been closed in #${prNumber}. The change will be included in the upcoming ${isDevelop ? "minor" : "patch"} release.`
 

docs/_static/versions.json

@@ -1 +1 @@
-{ "versions": ["1", "2", "main", "develop", "3-dev"], "latest": "2" }
+{ "versions": ["1", "2", "main", "3-dev"], "latest": "2" }