Skip to content

CI: pin the linters, so a release cannot turn a branch red #1115

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
thc1006 wants to merge 1 commit into from
+6 −1
Closed

CI: pin the linters, so a release cannot turn a branch red #1115

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .github/workflows/linters.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,12 @@ jobs:
python -m pip install --upgrade pip
pip install .[all]
pip install .[tests]
pip install pylint ruff
# Pinned, because both decide whether this job passes and both change
# what they report between releases. Unpinned, the formatter widening
# its scope or pylint adding a check turns a branch red with no commit
# to explain it. Bumping these is a deliberate change, made when the
# tree is ready for what the new version says.
pip install "pylint==4.0.6" "ruff==0.16.2"
- name: Ruff (lint)
run: ruff check --output-format=github .
- name: Ruff (format)
Expand Down
Loading