🛠️ fix(pyproject): update pyproject.toml (#3179)

* chore: update dependencies in pyproject.toml

* Replace "pre-commit" with "prek" in both root and application/backend pyproject.toml files.
* Remove dependency for "geti-inspect" in the root pyproject.toml.

Signed-off-by: Ashwin Vaidya <[email protected]>

* Update prek references

Signed-off-by: Ashwin Vaidya <[email protected]>

* Update uv.lock

Signed-off-by: Ashwin Vaidya <[email protected]>

---------

Signed-off-by: Ashwin Vaidya <[email protected]>

Author: ashwinvaidya17

.github/workflows/_reusable-code-quality.yaml

@@ -1,7 +1,7 @@
 # Code Quality Workflow
 #
-# This reusable workflow executes code quality checks using prek (pre-commit workspace tool)
-# with support for monorepo configurations and multiple pre-commit configs.
+# This reusable workflow executes code quality checks using prek (prek workspace tool)
+# with support for monorepo configurations and multiple prek configs.
 #
 # Key Features:
 # - Workspace mode support (multiple .pre-commit-config.yaml files)

.github/workflows/pre_merge.yml

@@ -34,7 +34,7 @@ jobs:
       - name: Install Tox
         run: pip install tox
       - name: Code quality checks
-        run: tox -e pre-commit
+        run: tox -e prek
   Pre-Merge-Checks:
     runs-on: [self-hosted, linux, x64, anomalib]
     needs: Code-Quality-Checks

CONTRIBUTING.md

@@ -69,15 +69,15 @@ Set up your development environment to start contributing. This involves install
 3. Install and configure pre-commit hooks:
 
    ```bash
-   pre-commit install
+   prek install
    ```
 
 Pre-commit hooks help ensure code quality and consistency. After each commit,
-`pre-commit` will automatically run the configured checks for the changed file.
+`prek` will automatically run the configured checks for the changed file.
 If you would like to manually run the checks for all files, use:
 
 ```bash
-pre-commit run --all-files
+prek run --all-files
 ```
 
 To bypass pre-commit hooks temporarily (e.g., for a work-in-progress commit),
@@ -102,7 +102,7 @@ However, make sure to address any pre-commit issues before finalizing your pull
 4. **Pass Tests and Quality Checks:** Ensure the test suite passes and that your code meets quality standards by running:
 
    ```bash
-   pre-commit run --all-files
+   prek run --all-files
    pytest tests/
    ```
 

application/backend/pyproject.toml

@@ -31,7 +31,7 @@ dependencies = [
 [dependency-groups]
 dev = [
     "pytest~=8.3",
-    "pre-commit~=4.1",
+    "prek",
     "pdbpp~=0.10",
     "flaky~=3.8",
     "testfixtures~=8.2",

application/backend/uv.lock

@@ -45,15 +45,15 @@ Set up your development environment to start contributing. This involves install
 2. Install and configure pre-commit hooks:
 
    ```bash
-   pre-commit install
+   prek install
    ```
 
    Pre-commit hooks help ensure code quality and consistency. After each commit,
-   `pre-commit` will automatically run the configured checks for the changed file.
+   `prek` will automatically run the configured checks for the changed file.
    If you would like to manually run the checks for all files, use:
 
    ```bash
-   pre-commit run --all-files
+   prek run --all-files
    ```
 
    To bypass pre-commit hooks temporarily (e.g., for a work-in-progress commit), use:
@@ -77,7 +77,7 @@ Set up your development environment to start contributing. This involves install
 4. **Pass Tests and Quality Checks:** Ensure the test suite passes and that your code meets quality standards by running:
 
    ```bash
-   pre-commit run --all-files
+   prek run --all-files
    pytest tests/
    ```
 

docs/source/markdown/guides/developer/contributing.md

@@ -86,7 +86,7 @@ docs = [
     "sphinx_design",
 ]
 test = [
-    "pre-commit",
+    "prek",
     "pytest",
     "pytest-cov",
     "pytest-xdist",
@@ -131,10 +131,6 @@ xpu = [
 ]
 full = ["anomalib[clip,openvino,loggers,notebooks,vlm,video]"]
 dev = ["anomalib[full,docs,test]"]
-# Geti Inspect application requires python>=3.13
-application = [
-    "geti-inspect ; python_version >= '3.13'"
-]
 
 [project.scripts]
 anomalib = "anomalib.cli.cli:main"
@@ -234,7 +230,6 @@ pytorch-triton-rocm = [
 pytorch-triton-xpu = [
     { index = "pytorch-xpu", extra = "xpu" },
 ]
-geti-inspect = { path = "./application/backend", editable = true }
 
 
 # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

pyproject.toml

@@ -10,7 +10,7 @@ Before running the tests, make sure you have the following prerequisites
 installed:
 
 - Python 3.8 or newer
-- `pre-commit`
+- `prek`
 - `pytest`
 - `pytest-cov`
 - `pytest-sugar`
@@ -93,7 +93,7 @@ This will provide instructions on how to check test coverage with `pytest-cov.`
 ensuring compatibility. In Anomalib, `tox` is used to automate multiple tests.
 Here's a brief explanation of each:
 
-- `pre-commit`: These tests are run before each commit is made to the
+- `prek`: These tests are run before each commit is made to the
   repository. They're used to catch issues early and prevent problematic code
   from being committed to the repository. They can include things like style
   checks, unit tests, and static analysis.
@@ -118,7 +118,7 @@ environment. Here are some examples:
 To run the pre-commit tests
 
 ```bash
-tox -e pre-commit
+tox -e prek
 ```
 
 To run the unit and integration tests

tests/README.md

@@ -2,7 +2,7 @@
 isolated_build = True
 skip_missing_interpreters = true
 envlist =
-    pre-commit
+    prek
     pre-merge-py{38,39,310}
     snyk-scan
 
@@ -12,7 +12,7 @@ passenv = ftp_proxy
     HTTPS_PROXY
     CUDA_VISIBLE_DEVICES
 
-[testenv:pre-commit]
+[testenv:prek]
 basepython = py310
 deps =
     prek