pymetadata 0.8.2__tar.gz → 0.8.3__tar.gz

{pymetadata-0.8.2 → pymetadata-0.8.3}/.bumpversion.toml

@@ -1,5 +1,5 @@
 [tool.bumpversion]
-current_version = "0.8.2"
+current_version = "0.8.3"
 commit = true
 parse = "(?P<major>\\d+)\\.(?P<minor>\\d+)\\.(?P<patch>\\d+)"
 serialize = ["{major}.{minor}.{patch}"]

{pymetadata-0.8.2 → pymetadata-0.8.3}/.github/workflows/ci-cd.yml

@@ -38,7 +38,7 @@ jobs:
         persist-credentials: false
     - name: Install uv and set the python version
       # astral-sh/setup-uv publishes no floating major tag beyond v7
-      uses: astral-sh/setup-uv@v10.2.0
+      uses: astral-sh/setup-uv@v10.3.3
       with:
         python-version: ${{ matrix.python-version }}
         # a release run restores no cache, which zizmor cannot tell from the
@@ -84,7 +84,7 @@ jobs:
       with:
         persist-credentials: false
     - name: Install uv
-      uses: astral-sh/setup-uv@v10.2.0
+      uses: astral-sh/setup-uv@v10.3.3
       with:
         python-version: "3.14"
         # a release is built from a clean state, never from a restored cache

{pymetadata-0.8.2 → pymetadata-0.8.3}/.github/workflows/docs.yml

@@ -32,7 +32,7 @@ jobs:
         if: github.ref == 'refs/heads/develop'
         uses: actions/configure-pages@v6
       - name: Install uv and set the python version
-        uses: astral-sh/setup-uv@v10.2.0
+        uses: astral-sh/setup-uv@v10.3.3
         with:
           python-version: "3.14"
           enable-cache: true

{pymetadata-0.8.2 → pymetadata-0.8.3}/.github/workflows/ty.yml

@@ -26,7 +26,7 @@ jobs:
         with:
           persist-credentials: false
       - name: Install uv and set the python version
-        uses: astral-sh/setup-uv@v10.2.0
+        uses: astral-sh/setup-uv@v10.3.3
         with:
           python-version: "3.14"
           enable-cache: true

{pymetadata-0.8.2 → pymetadata-0.8.3}/.pre-commit-config.yaml

@@ -39,7 +39,7 @@ repos:
 
 - repo: https://github.com/astral-sh/ruff-pre-commit
   # Ruff version.
-  rev: v0.16.6
+  rev: v0.17.3
   hooks:
     # Run the linter.
     - id: ruff-check
@@ -51,7 +51,7 @@ repos:
 
 - repo: https://github.com/astral-sh/ty-pre-commit
   # ty version.
-  rev: v0.0.78
+  rev: v0.0.95
   hooks:
     # Run the type checker on the whole project (see `[tool.ty]` in pyproject.toml).
     # `--extra dev` syncs the environment with the dev dependencies, so that the

{pymetadata-0.8.2 → pymetadata-0.8.3}/CITATION.cff

@@ -8,8 +8,8 @@ authors:
     given-names: "Matthias"
     orcid: "https://orcid.org/0000-0003-1725-179X"
     affiliation: "Humboldt-University Berlin, Faculty of Life Science, Institute for Biology, Biology, Berlin; University Lübeck; University Hospital Schleswig-Holstein, Campus Lübeck, First Department of Medicine, Germany"
-version: "0.8.2"
-date-released: "2026-10-05"
+version: "0.8.3"
+date-released: "2026-10-22"
 doi: "10.5281/zenodo.5308801"
 license: MIT
 repository-code: "https://github.com/matthiaskoenig/pymetadata"

{pymetadata-0.8.2 → pymetadata-0.8.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pymetadata
-Version: 0.8.2
+Version: 0.8.3
 Summary: pymetadata are python utilities for working with metadata.
 Project-URL: Homepage, https://matthiaskoenig.github.io/pymetadata
 Project-URL: Documentation, https://matthiaskoenig.github.io/pymetadata
@@ -38,7 +38,7 @@ Requires-Dist: pronto>=2.7.3; extra == 'dev'
 Requires-Dist: pytest-cov>=7.1.0; extra == 'dev'
 Requires-Dist: pytest>=9.1.1; extra == 'dev'
 Requires-Dist: ruff>=0.16.6; extra == 'dev'
-Requires-Dist: tox>=4.61.2; extra == 'dev'
+Requires-Dist: tox!=4.67.5,>=4.61.2; extra == 'dev'
 Requires-Dist: ty>=0.0.78; extra == 'dev'
 Requires-Dist: zensical>=0.0.60; extra == 'dev'
 Provides-Extra: ontology
@@ -66,7 +66,7 @@ If you have any questions or issues please [open an issue](https://github.com/ma
 
 If you use `pymetadata` please cite the archived software on [Zenodo](https://doi.org/10.5281/zenodo.5308801):
 
-> König, M. (2026). *pymetadata are python utilities for working with metadata* (Version 0.8.0) [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.23159552
+> König, M. (2026). *pymetadata are python utilities for working with metadata* (Version 0.8.2) [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.23555354
 
 ```bibtex
 @software{konig_pymetadata,
@@ -74,10 +74,10 @@ If you use `pymetadata` please cite the archived software on [Zenodo](https://do
   title     = {pymetadata are python utilities for working with metadata},
   year      = {2026},
   month     = oct,
-  version   = {0.8.0},
+  version   = {0.8.2},
   publisher = {Zenodo},
-  doi       = {10.5281/zenodo.23159552},
-  url       = {https://doi.org/10.5281/zenodo.23159552},
+  doi       = {10.5281/zenodo.23555354},
+  url       = {https://doi.org/10.5281/zenodo.23555354},
 }
 ```
 

{pymetadata-0.8.2 → pymetadata-0.8.3}/README.md

@@ -19,7 +19,7 @@ If you have any questions or issues please [open an issue](https://github.com/ma
 
 If you use `pymetadata` please cite the archived software on [Zenodo](https://doi.org/10.5281/zenodo.5308801):
 
-> König, M. (2026). *pymetadata are python utilities for working with metadata* (Version 0.8.0) [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.23159552
+> König, M. (2026). *pymetadata are python utilities for working with metadata* (Version 0.8.2) [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.23555354
 
 ```bibtex
 @software{konig_pymetadata,
@@ -27,10 +27,10 @@ If you use `pymetadata` please cite the archived software on [Zenodo](https://do
   title     = {pymetadata are python utilities for working with metadata},
   year      = {2026},
   month     = oct,
-  version   = {0.8.0},
+  version   = {0.8.2},
   publisher = {Zenodo},
-  doi       = {10.5281/zenodo.23159552},
-  url       = {https://doi.org/10.5281/zenodo.23159552},
+  doi       = {10.5281/zenodo.23555354},
+  url       = {https://doi.org/10.5281/zenodo.23555354},
 }
 ```
 

{pymetadata-0.8.2 → pymetadata-0.8.3}/docs/index.md

@@ -70,7 +70,7 @@ If you have any questions or issues please [open an issue](https://github.com/ma
 
 If you use `pymetadata` please cite the archived software on [Zenodo](https://doi.org/10.5281/zenodo.5308801):
 
-> König, M. (2026). *pymetadata are python utilities for working with metadata* (Version 0.8.0) [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.23159552
+> König, M. (2026). *pymetadata are python utilities for working with metadata* (Version 0.8.2) [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.23555354
 
 ```bibtex
 @software{konig_pymetadata,
@@ -78,10 +78,10 @@ If you use `pymetadata` please cite the archived software on [Zenodo](https://do
   title     = {pymetadata are python utilities for working with metadata},
   year      = {2026},
   month     = oct,
-  version   = {0.8.0},
+  version   = {0.8.2},
   publisher = {Zenodo},
-  doi       = {10.5281/zenodo.23159552},
-  url       = {https://doi.org/10.5281/zenodo.23159552},
+  doi       = {10.5281/zenodo.23555354},
+  url       = {https://doi.org/10.5281/zenodo.23555354},
 }
 ```
 

{pymetadata-0.8.2 → pymetadata-0.8.3}/pyproject.toml

@@ -59,7 +59,9 @@ dev = [
 	"ruff>=0.16.6",
 	"pre-commit>=4.6.2",
 	"ty>=0.0.78",
-    "tox>=4.61.2",
+    # 4.67.5 refuses its package staging directory when it was created under
+    # umask 002, tox-dev/tox#4357
+    "tox>=4.61.2,!=4.67.5",
     "pytest>=9.1.1",
     "pytest-cov>=7.1.0",
     "zensical>=0.0.60",

pymetadata-0.8.3/release-notes/0.8.3.md

@@ -0,0 +1,18 @@
+# Release notes for pymetadata 0.8.3
+![pymetadata](./docs/images/favicon/pymetadata-100x100-300dpi.png)
+
+## Security
+
+- The lock of the development environment, `uv.lock`, has filelock 4.2.6 instead of 4.1.0 (#111), which fixes the advisories of filelock before 4.2.1 ([GHSA-2g95-wg33-c5x2](https://github.com/advisories/GHSA-2g95-wg33-c5x2), [GHSA-v4x8-3wr5-3wq8](https://github.com/advisories/GHSA-v4x8-3wr5-3wq8), [GHSA-crv4-6mhj-j5jh](https://github.com/advisories/GHSA-crv4-6mhj-j5jh) and 14 more). filelock reaches only the development environment, through tox, virtualenv and python-discovery, so the dependencies of pymetadata are unchanged. virtualenv moves from 21.14.12 to 21.15.2.
+
+## Dependencies
+
+- The lock moves to the newest releases (#110, #111), among them certifi 2026.10.23, pydantic 2.14.2, pronto 2.7.4, ruff 0.17.3, ty 0.0.95, pytest 9.2.0, zensical 0.0.74 and mkdocstrings-python 2.0.10. The lower bounds in `pyproject.toml` are unchanged.
+
+## Development
+
+- The dev extra excludes tox 4.67.5 (`tox>=4.61.2,!=4.67.5`), the lock keeps tox 4.67.4 (#111). tox 4.67.5 refuses its package staging directory when tox created it under umask 002, so every environment of `tox run-parallel` in a fresh checkout fails with an internal error ([tox-dev/tox#4357](https://github.com/tox-dev/tox/issues/4357)).
+- The pre-commit hooks of ruff and ty follow the locked versions, ruff 0.17.3 and ty 0.0.95 (#111).
+- Continuous integration uses astral-sh/setup-uv 10.3.3 (#109).
+
+Your pymetadata team

{pymetadata-0.8.2 → pymetadata-0.8.3}/src/pymetadata/__init__.py

@@ -7,7 +7,7 @@ from pathlib import Path
 logging.getLogger(__name__).addHandler(logging.NullHandler())
 
 __author__ = "Matthias Koenig"
-__version__ = "0.8.2"
+__version__ = "0.8.3"
 
 
 program_name: str = "pymetadata"