STY: fixed pre-commit

Author: dmgav

.pre-commit-config.yaml

@@ -8,18 +8,18 @@ repos:
       - id: end-of-file-fixer
       - id: trailing-whitespace
   - repo: https://github.com/ambv/black
-    rev: 26.1.0
+    rev: 26.3.1
     hooks:
       - id: black
   - repo: https://github.com/pycqa/flake8
     rev: 7.3.0
     hooks:
       - id: flake8
   - repo: https://github.com/pycqa/isort
-    rev: 7.0.0
+    rev: 8.0.1
     hooks:
       - id: isort
   - repo: https://github.com/kynan/nbstripout
-    rev: 0.9.0
+    rev: 0.9.1
     hooks:
       - id: nbstripout

bluesky_queueserver/manager/utils.py

@@ -1,4 +1,3 @@
-
 def to_boolean(value):
     """
     Returns ``True`` or ``False`` if ``value`` is found in one of the lists of supported values.

docs/source/release_history.rst

@@ -10,14 +10,14 @@ Added
 -----
 
 - New ``re_metadata`` manager API endpoint that allows clients to query the current Run Engine metadata
-  dictionary. The metadata dictionary is filtered based on the list of permitted metadata keys defined 
+  dictionary. The metadata dictionary is filtered based on the list of permitted metadata keys defined
   in the manager configuration. If the list of permitted keys is empty, then all metadata keys are allowed.
 
 - New CLI command ``qserver re metadata`` for querying the current Run Engine metadata dictionary.
 
 - New ``permitted_re_metadata_keys`` parameter for RE Manager configuration that allows to control which
-  metadata keys are allowed to be included in the messages sent by Run Engine callbacks. 
-  The option can be set using CLI parameter ``--permitted-re-metadata-keys`` or environment variable 
+  metadata keys are allowed to be included in the messages sent by Run Engine callbacks.
+  The option can be set using CLI parameter ``--permitted-re-metadata-keys`` or environment variable
   ``QSERVER_PERMITTED_RE_METADATA_KEYS``.
 
 v0.0.24 (2026-01-21)