[pre-commit.ci] pre-commit autoupdate

.pre-commit-config.yaml

@@ -7,7 +7,7 @@ exclude: '.*\.jcad$'
 repos:
   # Autoformat and linting, misc. details
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v5.0.0
+    rev: v6.0.0
     hooks:
       - id: forbid-new-submodules
       - id: end-of-file-fixer
@@ -25,13 +25,13 @@ repos:
         exclude: .bumpversion.cfg
 
   # Autoformat: Python code
-  - repo: https://github.com/psf/black
-    rev: 25.1.0
+  - repo: https://github.com/psf/black-pre-commit-mirror
+    rev: 25.9.0
     hooks:
       - id: black
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.12.2
+    rev: v0.13.3
     hooks:
       - id: ruff
         args: ['--fix']
@@ -43,7 +43,7 @@ repos:
         args: ['--no-error-on-unmatched-pattern']
 
   - repo: https://github.com/pre-commit/mirrors-eslint
-    rev: v9.30.1
+    rev: v9.37.0
     hooks:
       - id: eslint
         files: \.tsx?$

RELEASE.md

@@ -82,7 +82,6 @@ Here is a summary of the steps to cut a new release:
 - If the repo generates PyPI release(s), create a scoped PyPI [token](https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#saving-credentials-on-github). We recommend using a scoped token for security reasons.
 
 - You can store the token as `PYPI_TOKEN` in your fork's `Secrets`.
-
   - Advanced usage: if you are releasing multiple repos, you can create a secret named `PYPI_TOKEN_MAP` instead of `PYPI_TOKEN` that is formatted as follows:
 
     ```text