tokenjam: ruff pinned <0.16 to unblock CI — triage the ~470 new ruff 0.16 default findings and unpin deliberately

Open
  • Is something wrong?
#567 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
ci-cd, tooling

Research direction

Start with tokenjam/pyproject.toml, where the dev-extra Ruff pin landed, and inspect the findings produced by Ruff 0.16 across the codebase. Triage the roughly 470 findings, fixing applicable ones and documenting ignored rule families. Done when Ruff has an explicit lint configuration, the pin is removed, and CI passes on current Ruff.

Written by the indexing model from the issue text.

Description

enhancement good first issue help wanted

Severity: Medium
Model: sonnet

Where: tokenjam/ — pyproject.toml dev extras (the ruff pin landed in PR 525), whole codebase for the findings
Observed: ruff 0.16.0 (released 2026-07-23/24 to PyPI) expanded ruff's default rule set. The repo has no [tool.ruff.lint] select/ignore block and ruff was unpinned in dev extras, so CI's Lint step started failing on ~470 pre-existing patterns that 0.15.x never flagged (main's last green run resolved 0.15.22; the branch resolved 0.16.0 cold). A worker pinned ruff<0.16 as a one-line unblock with an explanatory comment.
Done when: (1) an explicit [tool.ruff.lint] select/ignore config exists so the lint surface is version-stable by policy rather than by pin; (2) the ~470 ruff 0.16 findings are triaged — fix the real ones, explicitly ignore rule families that don't fit the codebase, with a short rationale comment per ignored family; (3) the ruff<0.16 pin is removed and CI is green on current ruff.

Dominant language
Python
Stars
122
Forks
35
Avg merge
4d 30m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Metabuilder-Labs/tokenjam

All issues in Metabuilder-Labs/tokenjam

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.