Update python for tests/pages and add poetry lockfile

.github/workflows/gh-pages.yml

@@ -35,7 +35,7 @@ jobs:
       - name: Install Python
         uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5.3.0
         with:
-          python-version: 3.12
+          python-version: 3.13
 
       - name: Install Poetry
         run: pip install poetry

.github/workflows/pr-run-tests.yml

@@ -20,7 +20,7 @@ jobs:
       - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
       - uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5.3.0
         with:
-          python-version: "3.12"
+          python-version: "3.13"
           cache: pip
       - name: Install poetry
         uses: abatilo/actions-poetry@e78f54a89cb052fff327414dd9ff010b5d2b4dbd # v3.0.1

.gitignore

@@ -165,4 +165,3 @@ cython_debug/
 # application files
 /artifacts
 /db.sqlite3*
-/poetry.lock

.pre-commit-config.yaml

@@ -1,7 +1,14 @@
 ci:
   skip:
+    - poetry-lock
     - pytest
 repos:
+  - repo: https://github.com/python-poetry/poetry
+    rev: 1.8.4
+    hooks:
+      - id: poetry-check
+      - id: poetry-lock
+      - id: poetry-install
   - repo: https://github.com/pre-commit/pre-commit-hooks
     rev: v5.0.0
     hooks:
@@ -49,7 +56,7 @@ repos:
       - id: biome-check
         additional_dependencies: ["@biomejs/biome@1.8.3"]
   - repo: https://github.com/rbubley/mirrors-prettier
-    rev: "v3.3.3"
+    rev: "v3.4.0"
     hooks:
       - id: prettier
         files: \.(html|md|yml|yaml)$

README.md

@@ -33,21 +33,21 @@ A simplistic, opinionated remote update server implementing hawkBit™'s [DDI AP
 
 Before running gooseBit for the first time, update the default credentials in `settings.yaml`. The default login for testing purposes is:
 
--   **Username:** `admin@goosebit.local`
--   **Password:** `admin`
+- **Username:** `admin@goosebit.local`
+- **Password:** `admin`
 
 ## Assumptions
 
--   Devices use [SWUpdate](https://swupdate.org) for managing software updates.
+- Devices use [SWUpdate](https://swupdate.org) for managing software updates.
 
 ## Features
 
 ### Device Registry
 
 When a device connects to gooseBit for the first time, it is automatically added to the device registry. The server will then request the device's configuration data, including:
 
--   `hw_model` and `hw_revision`: Used to match compatible software.
--   `sw_version`: Indicates the currently installed software version.
+- `hw_model` and `hw_revision`: Used to match compatible software.
+- `sw_version`: Indicates the currently installed software version.
 
 The registry tracks each device's status, including the last online timestamp, installed software version, update state, and more.
 
@@ -105,14 +105,14 @@ poetry run generate-sample-data
 
 Code is formatted using different tools
 
--   black and isort for `*.py`
--   biomejs for `*.js`, `*.json`
--   prettier for `*.html`, `*.md`, `*.yml`, `*.yaml`
+- black and isort for `*.py`
+- biomejs for `*.js`, `*.json`
+- prettier for `*.html`, `*.md`, `*.yml`, `*.yaml`
 
 Code is linted using different tools as well
 
--   flake8 for `*.py`
--   biomejs for `*.js`
+- flake8 for `*.py`
+- biomejs for `*.js`
 
 Best to have pre-commit install git hooks that run all those tools before a commit:
 
@@ -138,18 +138,18 @@ poetry run pytest
 
 The structure of gooseBit is as follows:
 
--   `api`: Files for the API.
--   `ui`: Files for the UI.
-    -   `bff`: Backend for frontend API.
-    -   `static`: Static files.
-    -   `templates`: Jinja2 formatted templates.
-    -   `nav`: Navbar handler.
--   `updater`: DDI API handler and device update manager.
--   `updates`: SWUpdate file parsing.
--   `auth`: Authentication functions and permission handling.
--   `models`: Database models.
--   `db`: Database config and initialization.
--   `schema`: Pydantic models used for API type hinting.
--   `settings`: Settings loader and handler.
--   `telemetry`: Telemetry data handlers.
--   `routes`: Routes for a giving endpoint, including the router.
+- `api`: Files for the API.
+- `ui`: Files for the UI.
+    - `bff`: Backend for frontend API.
+    - `static`: Static files.
+    - `templates`: Jinja2 formatted templates.
+    - `nav`: Navbar handler.
+- `updater`: DDI API handler and device update manager.
+- `updates`: SWUpdate file parsing.
+- `auth`: Authentication functions and permission handling.
+- `models`: Database models.
+- `db`: Database config and initialization.
+- `schema`: Pydantic models used for API type hinting.
+- `settings`: Settings loader and handler.
+- `telemetry`: Telemetry data handlers.
+- `routes`: Routes for a giving endpoint, including the router.

docs/development.md

@@ -28,16 +28,16 @@ poetry install --all-extras
 
 Code is formatted using different tools
 
--   black and isort for `*.py`
--   biomejs for `*.js`, `*.json`
--   prettier for `*.html`, `*.md`, `*.yml`, `*.yaml`
--   djlint for `*.html.jinja`
+- black and isort for `*.py`
+- biomejs for `*.js`, `*.json`
+- prettier for `*.html`, `*.md`, `*.yml`, `*.yaml`
+- djlint for `*.html.jinja`
 
 Code is linted using different tools as well
 
--   flake8 for `*.py`
--   biomejs for `*.js`
--   djlint for `*.html.jinja`
+- flake8 for `*.py`
+- biomejs for `*.js`
+- djlint for `*.html.jinja`
 
 Best to have pre-commit install git hooks that run all those tools before a commit:
 
@@ -63,18 +63,18 @@ poetry run pytest
 
 The structure of gooseBit is as follows:
 
--   `api`: Files for the API.
--   `ui`: Files for the UI.
-    -   `bff`: Backend for frontend API.
-    -   `static`: Static files.
-    -   `templates`: Jinja2 formatted templates.
-    -   `nav`: Navbar handler.
--   `updater`: DDI API handler and device update manager.
--   `updates`: SWUpdate file parsing.
--   `auth`: Authentication functions and permission handling.
--   `models`: Database models.
--   `db`: Database config and initialization.
--   `schema`: Pydantic models used for API type hinting.
--   `settings`: Settings loader and handler.
--   `telemetry`: Telemetry data handlers.
--   `routes`: Routes for a giving endpoint, including the router.
+- `api`: Files for the API.
+- `ui`: Files for the UI.
+    - `bff`: Backend for frontend API.
+    - `static`: Static files.
+    - `templates`: Jinja2 formatted templates.
+    - `nav`: Navbar handler.
+- `updater`: DDI API handler and device update manager.
+- `updates`: SWUpdate file parsing.
+- `auth`: Authentication functions and permission handling.
+- `models`: Database models.
+- `db`: Database config and initialization.
+- `schema`: Pydantic models used for API type hinting.
+- `settings`: Settings loader and handler.
+- `telemetry`: Telemetry data handlers.
+- `routes`: Routes for a giving endpoint, including the router.

docs/index.md

@@ -9,16 +9,16 @@ designed to make remote updates of embedded devices easier.
 
 ## Assumptions
 
--   Devices use [SWUpdate](https://swupdate.org) for managing software updates.
+- Devices use [SWUpdate](https://swupdate.org) for managing software updates.
 
 ## Features
 
 ### Device Registry
 
 When a device connects to gooseBit for the first time, it is automatically added to the device registry. The server will then request the device's configuration data, including:
 
--   `hw_model` and `hw_revision`: Used to match compatible software.
--   `sw_version`: Indicates the currently installed software version.
+- `hw_model` and `hw_revision`: Used to match compatible software.
+- `sw_version`: Indicates the currently installed software version.
 
 The registry tracks each device's status, including the last online timestamp, installed software version, update state, and more.
 

docs/quick_start.md

@@ -20,5 +20,5 @@ python main.py
 
 Before running gooseBit for the first time, update the default credentials in `settings.yaml`. The default login for testing purposes is:
 
--   **Username:** `admin@goosebit.local`
--   **Password:** `admin`
+- **Username:** `admin@goosebit.local`
+- **Password:** `admin`