Bump used package versions

.github/workflows/release.yml

@@ -5,7 +5,7 @@
 
 name: Upload Python Package
 
-on:
+on:  # yamllint disable-line rule:truthy
   push:
     branches:
       - main

.github/workflows/test-release.yaml

@@ -5,7 +5,7 @@
 
 name: Upload Python Package to test.pypi.org
 
-on: [pull_request]
+on: [pull_request]  # yamllint disable-line rule:truthy
 
 permissions:
   contents: write

.github/workflows/test.yml

@@ -7,7 +7,7 @@
 
 name: Test Python package
 
-on:
+on:  # yamllint disable-line rule:truthy
   push:
     # branches: [ $default-branch ]
     branches-ignore:

.github/workflows/unittest.yaml

@@ -5,7 +5,7 @@
 
 name: Unittest Python Package
 
-on: [push, pull_request]
+on: [push, pull_request]  # yamllint disable-line rule:truthy
 
 permissions:
   contents: read

.python-version

@@ -0,0 +1 @@
+3.9

changelog.md

@@ -17,6 +17,17 @@ r"^\#\# \[\d{1,}[.]\d{1,}[.]\d{1,}\] \- \d{4}\-\d{2}-\d{2}$"
 -->
 
 ## Released
+## [0.6.0] - 2026-04-27
+### Added
+- `.python-version` to use repo this with pyenv
+
+### Changed
+- Bump all package versions to their latest version supporting Python 3.9
+- Mention Python 3.11 and 3.12 support in `setup.py`
+
+### Fixed
+- Silence all yamllint warnings
+
 ## [0.5.1] - 2026-04-27
 ### Fixed
 - This change creates the correct release candidate number based on the action run of a pull request workflow run `test-release` instead of the total number of this workflow run. By this fix, the `-rcX` metadata starts at `1` and is incremented with every push, no matter if the push is a force push or a classic new commit on top in a ongoing pull request.
@@ -60,8 +71,9 @@ r"^\#\# \[\d{1,}[.]\d{1,}[.]\d{1,}\] \- \d{4}\-\d{2}-\d{2}$"
 - Not used files provided with [template repo](https://github.com/brainelectronics/micropython-i2c-lcd)
 
 <!-- Links -->
-[Unreleased]: https://github.com/brainelectronics/micropython-package-validation/compare/0.5.1...main
+[Unreleased]: https://github.com/brainelectronics/micropython-package-validation/compare/0.6.0...main
 
+[0.6.0]: https://github.com/brainelectronics/micropython-package-validation/tree/0.6.0
 [0.5.1]: https://github.com/brainelectronics/micropython-package-validation/tree/0.5.1
 [0.5.0]: https://github.com/brainelectronics/micropython-package-validation/tree/0.5.0
 [0.4.0]: https://github.com/brainelectronics/micropython-package-validation/tree/0.4.0

setup.py

@@ -99,6 +99,8 @@
         "Programming Language :: Python :: 3.8",
         "Programming Language :: Python :: 3.9",
         "Programming Language :: Python :: 3.10",
+        "Programming Language :: Python :: 3.11",
+        "Programming Language :: Python :: 3.12",
         "Programming Language :: Python :: 3 :: Only",
     ],
     license="MIT",
@@ -136,9 +138,9 @@
     # For an analysis of "install_requires" vs pip's requirements files see:
     # https://packaging.python.org/discussions/install-requires-vs-requirements/
     install_requires=[
-        "changelog2version>=0.9.0,<1",
-        "deepdiff>=6.3.0,<7",
-        "mock>=4.0.3,<5",
+        "changelog2version>=0.12.1,<1",
+        "deepdiff>=8.6.2,<9",
+        "mock>=5.2.0,<6",
     ],  # Optional
     # List additional groups of dependencies here (e.g. development
     # dependencies). Users will be able to install these using the "extras"
@@ -150,13 +152,13 @@
     # projects.
     extras_require={  # Optional
         "dev": [
-            "tox>=3.25.1,<4"
+            "tox>=4.30,<5"
         ],
         "test": [
-            "flake8>=5.0.0,<6",
-            "coverage>=6.4.2,<7",
-            "nose2>=0.12.0,<1",
-            "yamllint>=1.29,<2"
+            "flake8>=7.3.0,<8",
+            "coverage>=7.10,<8",
+            "nose2>=0.16.0,<1",
+            "yamllint>=1.37,<2"
         ],
     },
     # If there are data files included in your packages that need to be