From a3969417a97939576b42a9ce2152d1060450b875 Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
 <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Mon, 19 Feb 2024 23:48:51 +0000
Subject: [PATCH 1/5] [pre-commit.ci] pre-commit autoupdate
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

updates:
- [github.com/psf/black: 24.1.1 → 24.2.0](https://github.com/psf/black/compare/24.1.1...24.2.0)
- [github.com/python-jsonschema/check-jsonschema: 0.27.4 → 0.28.0](https://github.com/python-jsonschema/check-jsonschema/compare/0.27.4...0.28.0)
---
 .pre-commit-config.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index c8b2e4948..f86da5b72 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -2,7 +2,7 @@ repos:
 
 
 - repo: https://github.com/psf/black
-  rev: 24.1.1  # IF VERSION CHANGES --> MODIFY "blacken-docs" MANUALLY AS WELL!!
+  rev: 24.2.0  # IF VERSION CHANGES --> MODIFY "blacken-docs" MANUALLY AS WELL!!
   hooks:
   - id: black
     args: [
@@ -44,7 +44,7 @@ repos:
   - id: debug-statements
 
 - repo: https://github.com/python-jsonschema/check-jsonschema
-  rev: 0.27.4
+  rev: 0.28.0
   hooks:
     - id: check-github-workflows
       name: "Check GitHub workflows"

From be0e5e06445f150aa19792675509e389c64a736e Mon Sep 17 00:00:00 2001
From: Roberto Pastor Muela <37798125+RobPasMue@users.noreply.github.com>
Date: Tue, 20 Feb 2024 08:05:44 +0100
Subject: [PATCH 2/5] Update .pre-commit-config.yaml

---
 .pre-commit-config.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index f86da5b72..dc9ccc6bb 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -14,7 +14,7 @@ repos:
   rev: 1.16.0
   hooks:
   - id: blacken-docs
-    additional_dependencies: [black==24.1.1]
+    additional_dependencies: [black==24.2.0]
 
 - repo: https://github.com/pycqa/isort
   rev: 5.13.2

From f0acb39b78a46c45210fb70ff86dfd26f349024e Mon Sep 17 00:00:00 2001
From: Roberto Pastor Muela <37798125+RobPasMue@users.noreply.github.com>
Date: Tue, 20 Feb 2024 08:12:09 +0100
Subject: [PATCH 3/5] Update deprecation.rst

---
 doc/source/coding-style/deprecation.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/source/coding-style/deprecation.rst b/doc/source/coding-style/deprecation.rst
index e6f2041dc..80175c045 100644
--- a/doc/source/coding-style/deprecation.rst
+++ b/doc/source/coding-style/deprecation.rst
@@ -2,7 +2,7 @@ Deprecation best practices
 ==========================
 
 While deprecation best practices are outlined in a `Stack
-Overflow Answer <https://stackoverflow.com/questions/2536307>`_ and
+Overflow Answer <https://stackoverflow.com/questions/2536307/decorators-in-the-python-standard-lib-deprecated-specifically>`_ and
 in this `Deprecation library <https://deprecation.readthedocs.io/>`_ ,
 there is no official guidance on deprecating features within Python.
 Thus, this topic provides deprecation best practices for PyAnsys
@@ -93,4 +93,4 @@ You then use this custom ``DeprecationError`` in place of an ``Exception``.
             This function has been deprecated.
 
         """
-        raise DeprecationError('`my_function` has been deprecated.')
\ No newline at end of file
+        raise DeprecationError('`my_function` has been deprecated.')

From d5755d18fa4087d3925f307a2cd1b16b590d3572 Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
 <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Tue, 20 Feb 2024 07:12:18 +0000
Subject: [PATCH 4/5] [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci
---
 doc/source/coding-style/deprecation.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/source/coding-style/deprecation.rst b/doc/source/coding-style/deprecation.rst
index 80175c045..2f91461d8 100644
--- a/doc/source/coding-style/deprecation.rst
+++ b/doc/source/coding-style/deprecation.rst
@@ -93,4 +93,4 @@ You then use this custom ``DeprecationError`` in place of an ``Exception``.
             This function has been deprecated.
 
         """
-        raise DeprecationError('`my_function` has been deprecated.')
+        raise DeprecationError("`my_function` has been deprecated.")

From 889e81b7704cab995e5692c045b0629260be0ba7 Mon Sep 17 00:00:00 2001
From: Roberto Pastor Muela <37798125+RobPasMue@users.noreply.github.com>
Date: Tue, 20 Feb 2024 08:20:48 +0100
Subject: [PATCH 5/5] fix: remove stackoverflow link

---
 doc/source/coding-style/deprecation.rst | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/doc/source/coding-style/deprecation.rst b/doc/source/coding-style/deprecation.rst
index 2f91461d8..e46c73b49 100644
--- a/doc/source/coding-style/deprecation.rst
+++ b/doc/source/coding-style/deprecation.rst
@@ -1,9 +1,8 @@
 Deprecation best practices
 ==========================
 
-While deprecation best practices are outlined in a `Stack
-Overflow Answer <https://stackoverflow.com/questions/2536307/decorators-in-the-python-standard-lib-deprecated-specifically>`_ and
-in this `Deprecation library <https://deprecation.readthedocs.io/>`_ ,
+While deprecation best practices are outlined in 
+this `Deprecation library <https://deprecation.readthedocs.io/>`_ ,
 there is no official guidance on deprecating features within Python.
 Thus, this topic provides deprecation best practices for PyAnsys
 libraries.