Update dependency updates

.pre-commit-config.yaml

@@ -87,12 +87,12 @@ repos:
       - id: search-and-replace
         language_version: default # https://github.com/mattlqx/pre-commit-search-and-replace/issues/28
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.16.0
+    rev: v0.16.1
     hooks:
       - id: ruff-format
       - id: ruff-check
   - repo: https://github.com/astral-sh/uv-pre-commit
-    rev: 0.11.32
+    rev: 0.12.2
     hooks:
       - id: uv-lock
       - id: uv-audit
@@ -135,7 +135,7 @@ repos:
         args:
           - --strict
   - repo: https://github.com/astral-sh/ty-pre-commit
-    rev: v0.0.63
+    rev: v0.0.68
     hooks:
       - id: ty
   - repo: https://github.com/asottile/pyupgrade
@@ -154,18 +154,18 @@ repos:
     hooks:
       - id: actionlint
   - repo: https://github.com/crate-ci/typos
-    rev: v1.48.0
+    rev: v1.49.0
     hooks:
       - id: typos
         exclude_types:
           - svg
   - repo: https://github.com/rvben/rumdl-pre-commit
-    rev: v0.2.43
+    rev: v0.2.52
     hooks:
       - id: rumdl-fmt
         language: python # ensures that Renovate can update additional_dependencies
         additional_dependencies:
-          - shuck-cli==0.0.45
+          - shuck-cli==0.1.1
       - id: rumdl
   - repo: https://github.com/jendrikseipp/vulture
     rev: v2.16
@@ -181,7 +181,7 @@ repos:
     hooks:
       - id: shfmt
   - repo: https://github.com/ewhauser/shuck
-    rev: v0.0.45
+    rev: v0.1.1
     hooks:
       - id: shuck
         args:

README.md

@@ -1,9 +1,7 @@
 # Dev Tools
 
-<!-- rumdl-disable MD013 -->
 [![Check](https://github.com/hofbi/dev-tools/actions/workflows/check.yaml/badge.svg)](https://github.com/hofbi/dev-tools/actions/workflows/check.yaml)
 [![pre-commit.ci status](https://results.pre-commit.ci/badge/github/hofbi/dev-tools/master.svg)](https://results.pre-commit.ci/latest/github/hofbi/dev-tools/master)
-<!-- rumdl-enable MD013 -->
 
 This is a collection of Luminar's development tools.
 These tools are used to help developers in their day-to-day tasks.

packages/configure_vscode_for_bazel/README.md

@@ -1,10 +1,8 @@
 # Configure-Vscode-for-Bazel
 
-<!-- rumdl-disable MD013 -->
 [![PyPI](https://img.shields.io/pypi/v/configure-vscode-for-bazel)](https://pypi.org/project/configure-vscode-for-bazel/)
 [![PyPI - Python Version](https://img.shields.io/pypi/pyversions/configure-vscode-for-bazel)](https://pypi.org/project/configure-vscode-for-bazel/)
 [![PyPI - License](https://img.shields.io/pypi/l/configure-vscode-for-bazel)](https://pypi.org/project/configure-vscode-for-bazel/)
-<!-- rumdl-enable MD013 -->
 
 If you want to work with C++ Bazel targets in VS Code, you can use `configure-vscode-for-bazel` to generate a VS Code configuration.
 This tool supports generating:

packages/pre_commit_excludes/README.md

@@ -1,10 +1,8 @@
 # Pre-Commit-Excludes
 
-<!-- rumdl-disable MD013 -->
 [![PyPI](https://img.shields.io/pypi/v/pre-commit-excludes)](https://pypi.org/project/pre-commit-excludes/)
 [![PyPI - Python Version](https://img.shields.io/pypi/pyversions/pre-commit-excludes)](https://pypi.org/project/pre-commit-excludes/)
 [![PyPI - License](https://img.shields.io/pypi/l/pre-commit-excludes)](https://pypi.org/project/pre-commit-excludes/)
-<!-- rumdl-enable MD013 -->
 
 `remove-unnecessary-excludes` should help you to find lines in your exclude list that are no longer required.
 Running this tool will try to remove excludes from your config by removing a line, running the hook, and restore the old config if it is still required.

packages/whoowns/README.md

@@ -1,10 +1,8 @@
 # Whoowns
 
-<!-- rumdl-disable MD013 -->
 [![PyPI](https://img.shields.io/pypi/v/whoowns)](https://pypi.org/project/whoowns/)
 [![PyPI - Python Version](https://img.shields.io/pypi/pyversions/whoowns)](https://pypi.org/project/whoowns/)
 [![PyPI - License](https://img.shields.io/pypi/l/whoowns)](https://pypi.org/project/whoowns/)
-<!-- rumdl-enable MD013 -->
 
 `whoowns` is a tool to print the GitHub codeowner of a folder or file by parsing the `CODEOWNERS` file.
 With this tool, you can easily find out who is responsible for a specific part of the codebase from the terminal.