Finalize stage-2 migration: bump dependencies and clean up Codeberg references #22
marvin8
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/stage2-migration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Finalizes the stage-2 migration for kokopelli (forge.marvin8.zone).
Changes
~=minimums per zaojun: typer 0.27.1, whenever 0.10.5, bump-my-version 1.5.1, complexipy 7.0.0, prek 0.4.13, ruff 0.16.2, ty 0.0.70, uv 0.12.3.uv.lockandpylock.toml.CLAUDE.mdto forge.marvin8.zone / Forge.Validation
nox -s pysentry— 0 vulnerabilities foundnox -s pytest— 68 passed on Python 3.11/3.12/3.13/3.14/3.14tty check .,complexipy .,ruff format --check .,ruff check src/— all passnox -s deptry interrogate dependency_versions— all passWuMing
Found 4 issue(s). See inline comments below.
@ -12,3 +12,3 @@- repo: https://github.com/astral-sh/ruff-pre-commitrev: v0.15.21rev: v0.16.2config [MEDIUM]
Pre-commit ruff hook is pinned to v0.16.2, but the regenerated lock files resolve ruff to 0.16.3. Pre-commit will therefore run a different ruff version than the local
uv/nox environment, which can cause inconsistent lint or formatting results. Update the rev to v0.16.3 (or pin the lock to exactly 0.16.2).@ -22,3 +22,3 @@- repo: https://github.com/astral-sh/ty-pre-commitrev: v0.0.57rev: v0.0.70config [MEDIUM]
Pre-commit ty hook is pinned to v0.0.70, while the lock files resolve ty to 0.0.72. Align the rev with the locked version so pre-commit and local type checking use the same tool version.
@ -27,3 +27,3 @@- repo: https://github.com/astral-sh/uv-pre-commitrev: 0.11.28rev: 0.12.3config [MEDIUM]
uv-pre-commit hook is pinned to 0.12.3, but the lock files resolve uv to 0.12.5. Since this hook runs
uv lock/uv export, using an older uv version can produce different lockfile metadata/resolution than the version used to regenerate the lock files. Update the rev to 0.12.5.@ -39,3 +39,3 @@- repo: https://github.com/rohaquinlop/complexipy-pre-commitrev: v5.1.0rev: v7.0.0config [MEDIUM]
complexipy pre-commit hook is pinned to v7.0.0, but pylock.toml resolves complexipy to 7.0.1. Update the rev to v7.0.1 (or pin the dependency to exactly 7.0.0) so pre-commit uses the same version as the validated environment.
.pre-commit-config.yamlline 14🔴 Pre-commit revs are pinned to the version chosen for
pyproject.toml(the~=minimum). Per the project AGENTS.md,uv syncresolving a newer patch within the~=range is fine — pre-commit runs in its own isolated environment, so the rev does not need to match the installed version exactly..pre-commit-config.yamlline 24🔴 Pre-commit revs are pinned to the version chosen for
pyproject.toml(the~=minimum). Per the project AGENTS.md,uv syncresolving a newer patch within the~=range is fine — pre-commit runs in its own isolated environment, so the rev does not need to match the installed version exactly..pre-commit-config.yamlline 29🔴 Pre-commit revs are pinned to the version chosen for
pyproject.toml(the~=minimum). Per the project AGENTS.md,uv syncresolving a newer patch within the~=range is fine — pre-commit runs in its own isolated environment, so the rev does not need to match the installed version exactly..pre-commit-config.yamlline 41🔴 Pre-commit revs are pinned to the version chosen for
pyproject.toml(the~=minimum). Per the project AGENTS.md,uv syncresolving a newer patch within the~=range is fine — pre-commit runs in its own isolated environment, so the rev does not need to match the installed version exactly.