chore(backend): bump devtools (#9088)

* chore(backend):Bump devtools

* fix typos that are now detected

.pre-commit-config.yaml

@@ -17,7 +17,7 @@ repos:
     -   id: check-yaml
     -   id: mixed-line-ending
 -   repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.9.2
+    rev: v0.9.6
     hooks:
     - id: ruff-format
       args: [--preview]
@@ -28,7 +28,7 @@ repos:
         --preview
       ]
 -   repo: https://github.com/astral-sh/uv-pre-commit
-    rev: 0.5.20
+    rev: 0.6.0
     hooks:
       - id: pip-compile
         name: pip-compile requirements-dev.in
@@ -55,7 +55,7 @@ repos:
     hooks:
       - id: djlint-django
 - repo: https://github.com/codespell-project/codespell
-  rev: v2.3.0
+  rev: v2.4.1
   hooks:
   - id: codespell
     additional_dependencies:
@@ -76,7 +76,7 @@ repos:
         additional_dependencies: ["@biomejs/biome@1.9.4"]
         files: ^src/frontend/.*\.(js|ts|tsx)$
 -   repo: https://github.com/gitleaks/gitleaks
-    rev: v8.23.2
+    rev: v8.23.3
     hooks:
     -   id: gitleaks
         language_version: 1.23.6

docs/docs/part/template.md

@@ -6,7 +6,7 @@ title: Part Templates
 
 There are various purposes for using Part Templates, among them:
 
-* Template parts can hold information that can be re-used across "Variants", a template part could be useful for creating a base variant of an assembly which can be derived from, with BoM changes for instance.
+* Template parts can hold information that can be reused across "Variants", a template part could be useful for creating a base variant of an assembly which can be derived from, with BoM changes for instance.
 * Variants can be used as "manufacturing variants" where the variant dictates a particular configuration which a customer can order: a variant might determine the particular options that come with a part, like harnesses, enclosure, color, specs, etc.
 
 "Variants" parts will reference the "Template" part therefore explicitly creating and showing direct relationship.

docs/docs/report/templates.md

@@ -182,7 +182,7 @@ Asset files can be rendered directly into the template as follows
 
 ## Report Snippets
 
-A powerful feature provided by the django / WeasyPrint templating framework is the ability to include external template files. This allows commonly used template features to be broken out into separate files and re-used across multiple templates.
+A powerful feature provided by the django / WeasyPrint templating framework is the ability to include external template files. This allows commonly used template features to be broken out into separate files and reused across multiple templates.
 
 To support this, InvenTree provides report "snippets" - short (or not so short) template files which cannot be rendered by themselves, but can be called from other templates.
 

src/backend/InvenTree/order/models.py

@@ -1716,7 +1716,7 @@ class PurchaseOrderLineItem(OrderLineItem):
         return max(r, 0)
 
     def is_completed(self) -> bool:
-        """Determine if this lien item has been fully received."""
+        """Determine if this line item has been fully received."""
         return self.received >= self.quantity
 
     def update_pricing(self):

src/backend/InvenTree/part/models.py

@@ -3369,7 +3369,7 @@ class PartStocktakeReport(models.Model):
         return os.path.basename(self.report.name)
 
     def get_absolute_url(self):
-        """Return the URL for the associaed report file for download."""
+        """Return the URL for the associated report file for download."""
         if self.report:
             return self.report.url
         return None

src/backend/InvenTree/stock/models.py

@@ -442,7 +442,7 @@ class StockItem(
 
     tags = TaggableManager(blank=True)
 
-    # A Query filter which will be re-used in multiple places to determine if a StockItem is actually "in stock"
+    # A Query filter which will be reused in multiple places to determine if a StockItem is actually "in stock"
     # See also: StockItem.in_stock() method
     IN_STOCK_FILTER = Q(
         quantity__gt=0,