Merge branch 'main' into patch-1

.pre-commit-config.yaml

@@ -3,6 +3,4 @@ repos:
     rev: v0.1.13
     hooks:
       - id: ruff
-        exclude: rednotebook/external/.*\.py
       - id: ruff-format
-        exclude: rednotebook/external/.*\.py

CHANGELOG.md

@@ -1,9 +1,8 @@
-# next (unreleased)
+# 2.12 (2024-09-17)
 
-* Use `ruff` for linting (Anh Trinh, #347).
-* Use `ruff` for formatting (Anh Trinh, #349).
+* Use `ruff` for linting and formatting (Anh Trinh, #347, #349).
 * Replace `tox` by `pre-commit` for linting and formatting (Anh Trinh, #349).
-* Add `--config` flag to specify path to pyproject.toml configuration file (Glen Robertson #352).
+* Add `--config` flag to specify path to pyproject.toml configuration file (Glen Robertson, #352).
 * Add version badges for PyPI and conda-forge to the README (Trevor James Smith, #356).
 
 # 2.11 (2024-01-06)

README.md

@@ -191,7 +191,7 @@ Vulture will automatically look for a `pyproject.toml` in the current working di
 
 To use a `pyproject.toml` in another directory, you can use the `--config path/to/pyproject.toml` flag.
 
-## Version control integration
+## Integrations
 
 You can use a [pre-commit](https://pre-commit.com/#install) hook to run
 Vulture before each commit. For this, install pre-commit and add the
@@ -209,6 +209,8 @@ Then run `pre-commit install`. Finally, create a `pyproject.toml` file
 in your repository and specify all files that Vulture should check under
 `[tool.vulture] --> paths` (see above).
 
+There's also a [GitHub Action for Vulture](https://github.com/gtkacz/vulture-action).
+
 ## How does it work?
 
 Vulture uses the `ast` module to build abstract syntax trees for all

vulture/version.py

@@ -1 +1 @@
-__version__ = "2.11"
+__version__ = "2.12"