chore: align ruff-pre-commit pin in .pre-commit-config.yaml with pyproject.toml (ruff==0.17.3)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
Research direction
Read .pre-commit-config.yaml and pyproject.toml to compare the Ruff pins. Update the astral-sh/ruff-pre-commit hook revision to v0.17.3 so it matches ruff==0.17.3, then check the diff. Done when both pins match; the issue notes that .pre-commit-config.yaml is a protected path requiring the agent-approved label on an agent-authored PR.
Written by the indexing model from the issue text.
Description
Loose end from #1197 (noted there as out of scope):
.pre-commit-config.yaml pins the ruff-pre-commit hook at rev: v0.16.1, while pyproject.toml pins ruff==0.17.3 for the CI lint job (ruff check .). If pre-commit and CI ever run different ruff versions, they can disagree on findings (new rules/behavior between 0.16.1 and 0.17.3).
Proposed solution
Bump the rev: of the astral-sh/ruff-pre-commit repo in .pre-commit-config.yaml to the release matching ruff==0.17.3 (v0.17.3), so local pre-commit and CI lint run the same ruff. Optionally add a CI/pre-commit consistency note so future ruff bumps update both pins together.
Notes
.pre-commit-config.yamlis a protected path per AGENT.md "Agent approval policy": an agent-authored PR touching it needs theagent-approvedlabel (human approval).- No milestone inherited: #1197 has none.
Estimated effort: < 1 hour (size:small).
- Dominant language
- Python
- Stars
- 8
- Forks
- 12
- Avg merge
- 11h 56m
- Merged PRs (30d)
- 190
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RonaldHensbergen/composable-data-stack
-
area:cli area:configuration documentation priority:low size:small
Difficulty 1/5 1-3 hours Newbie friendliness 80/100
RonaldHensbergen/composable-data-stack#1222 ·
Maintainers usually reply within 1 day
-
area:security priority:low size:small
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
RonaldHensbergen/composable-data-stack#1217 ·
Maintainers usually reply within 1 day
-
area:docs enhancement priority:low size:small
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
RonaldHensbergen/composable-data-stack#1114 ·
Maintainers usually reply within 1 day
-
area:docs documentation priority:low size:small
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
RonaldHensbergen/composable-data-stack#944 ·
Maintainers usually reply within 1 day
-
area:cli priority:low refactor size:small
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
RonaldHensbergen/composable-data-stack#915 ·
Maintainers usually reply within 1 day
All issues in RonaldHensbergen/composable-data-stack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
marimo-team/marimo#11768 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
btclib-org/btclib-node#2358 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 7 days
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MTSWebServices/RecTools#330 ·