chore: adopt ty and the modern-python self-hosted CI convention#15
Merged
Conversation
Drop the stale MyPy Strict badge (project now type-checks with ty, which has no badge in the convention) and replace the Codecov badge with the static coverage-100% badge linking to ci.yml, matching modern-di-fastapi (the self-hosted CI enforces --cov-fail-under=100 with no codecov upload).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Aligns
fast-version's tooling with themodern-pythonorg convention (as realized in the canonical siblingmodern-di-fastapi):[tool.mypy]; lint group is nowty, ruff, eof-fixer, typing-extensions. The four# type: ignore[...]sites are converted to their ty codes (invalid-argument-type,invalid-assignment,invalid-type-form×2). ty runs on defaults; it stays unpinned sinceuv.lockis git-ignored andjust installrunsuv lock --upgrade.workflow.ymlwithci.yml→_checks.yml(lint + pytest matrix 3.10–3.14), tag-drivenrelease.ymlon OIDC Trusted Publishing (noPYPI_TOKEN, also cuts a GitHub Release), andscheduled.yml(weekly dep-drift check that opens a tracking issue) +.github/scripts/report-scheduled-failure.sh.Justfileconvention recipes (lint/lint-ci/test-ci/test-branch/OIDCpublish), rufffix=false/unsafe-fixes=true+docstring-code-format, coverage moved out ofaddoptsintotest-ciwith--cov-fail-under=100,[tool.coverage.report], and theuv_build>=0.11,<1.0floor.CLAUDE.mdupdated to describe ty + the self-hosted CI.Operations prerequisite (required before the first tag)
release.ymlpublishes via OIDC, so before cutting the first tag after this merges, configure a PyPI Trusted Publisher for thefast-versionproject: environmentpypi, workflowrelease.yml, repositorycommunity-of-python/fast-version. Without it, a tag push fails atjust publish. Because publish runs before the GitHub Release step, a failed publish will not create a Release for an unpublished version.Verification
just lint-ci— eof-fixer, ruff format/check,ty check, and the planning index check all pass.just test-ci— 20 passed, 100% coverage (--cov-fail-under=100holds).Out of scope (design Non-goals)
pyproject
[project.urls]/classifiers/keywords ("Repository metadata" convention) and the deadpackages=[...]key are intentionally untouched — separate follow-up.Planning bundle:
planning/changes/2026-07-02.02-ty-and-ci-convention/.