Merge branch 'main' into pr-scipy

Author: bmhowe23

.github/PULL_REQUEST_TEMPLATE.md

@@ -48,9 +48,6 @@ through and explain.
 - [ ] Public-facing APIs have Doxygen docs.
 - [ ] User-visible behavior changes have public docs, or a follow-up is
       tracked.
-- [ ] User-facing docs for new features are in a **separate PR** held until
-      release (the docs site publishes immediately on merge to the default
-      branch, so feature docs must not land before the feature ships).
 
 ### Code style
 - [ ] Naming follows the existing convention (`snake_case` vs `camelCase`) for

.github/workflows/docs.yaml

@@ -113,23 +113,24 @@ jobs:
         with:
           path: build/docs/build/
 
-  deploy:
-    name: Deploy latest docs
-    if: |
-      github.ref == 'refs/heads/main' &&
-      (
-        github.event_name == 'push' ||
-        inputs.deploy_docs == true
-      )
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-    runs-on: ubuntu-latest
-    permissions:
-      pages: write
-      id-token: write
-    needs: build
-    steps:
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v4
+  # Disable for now, re-enable closer to release.
+  # deploy:
+  #   name: Deploy latest docs
+  #   if: |
+  #     github.ref == 'refs/heads/main' &&
+  #     (
+  #       github.event_name == 'push' ||
+  #       inputs.deploy_docs == true
+  #     )
+  #   environment:
+  #     name: github-pages
+  #     url: ${{ steps.deployment.outputs.page_url }}
+  #   runs-on: ubuntu-latest
+  #   permissions:
+  #     pages: write
+  #     id-token: write
+  #   needs: build
+  #   steps:
+  #     - name: Deploy to GitHub Pages
+  #       id: deployment
+  #       uses: actions/deploy-pages@v4

Contributing.md

@@ -85,16 +85,6 @@ this section is the authoritative source.
   required.
 - If public docs were not created for a user-visible change, **report and track
   that they still need to be written.**
-- **Docs for new features go in a separate PR, held until release.** Our
-  published documentation site updates immediately when changes land on the
-  default branch, so user-facing docs that describe a feature must not be
-  merged before the feature is actually available in a release. The
-  recommended flow is:
-  1. Merge the code change (with Doxygen / API reference updates only).
-  2. Open a follow-up PR that adds the user-facing docs (guides, tutorials,
-     release notes, examples).
-  3. Keep that docs PR in Draft / on hold and merge it at release time so
-     the published site and the released bits go live together.
 
 ### Code style