Skip to content

Keep development tooling locked and maintained - #3

Merged
KyleDerZweite merged 1 commit into
mainfrom
maintenance/locked-tooling-20261028-115756
Oct 28, 2026
Merged

KyleDerZweite merged 1 commit into
mainfrom
maintenance/locked-tooling-20261028-115756

Conversation

@KyleDerZweite

Copy link
Copy Markdown
Owner

Development checks could resolve different tool versions, and dependency maintenance was manual. This combines the compatible development dependency refresh with locked local/CI commands, immutable Action pins, a tested uv version, and weekly native uv and GitHub Actions updates. Runtime dependencies, product behavior, deployment safeguards, and support claims remain unchanged.

The reviewed scope updates pytest 9.1.1 to 9.2.0, Ruff 0.16.7 to 0.17.3, iniconfig 2.3.0 to 2.3.1, and pluggy 1.6.0 to 1.7.0 within existing constraints. It pins checkout v7.0.1, setup-uv v10.3.2, and uv 0.11.16. README and validation evidence describe deliberate lockfile refresh and remaining limits. No open PR overlapped this slice.

Validation on the committed content:

  • Fresh delivery checks on Python 3.14.8 passed 83 tests with 20 opt-in integration cases skipped, Ruff lint and formatting, offline lock consistency, both YAML parses, and Git whitespace checks.
  • Earlier implementation checks passed locked sync, tests and Ruff on Python 3.11.17 and 3.14.8, plus source-distribution/wheel build and exact artifact inspection. The independent review found no material findings.
  • The initial build included a temporary test environment and failed on external symlinks. Removing that environment resolved it. An initial inspection selected an older artifact; inspection of the exact new artifacts passed.

Fresh GitHub CI is pending. Real Docker/Podman integration and deployment were not run for this maintenance slice. Existing consumer, template, data, and Podman/SELinux limitations remain in force. The earlier vulnerability-alert inventory was empty, but dependency-analysis completeness remains unknown. No repository settings were changed during delivery.

Created with GPT-6.1-Sol in T3 Code through the Codex harness.

@KyleDerZweite
KyleDerZweite marked this pull request as ready for review October 28, 2026 16:19
@KyleDerZweite
KyleDerZweite merged commit bf683c6 into main Oct 28, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant