Skip to content
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.

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

[pre-commit.ci] pre-commit autoupdate #402

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

pre-commit-ci bot and others added 2 commits October 17, 2024 14:02
updates:
- [github.com/pre-commit/pre-commit-hooks: v4.6.0 → v5.0.0](pre-commit/pre-commit-hooks@v4.6.0...v5.0.0)
- [github.com/asottile/pyupgrade: v3.16.0 → v3.17.0](asottile/pyupgrade@v3.16.0...v3.17.0)
- [github.com/adamchainz/django-upgrade: 1.19.0 → 1.21.0](adamchainz/django-upgrade@1.19.0...1.21.0)
- [github.com/psf/black-pre-commit-mirror: 24.4.2 → 24.10.0](psf/black-pre-commit-mirror@24.4.2...24.10.0)
- [github.com/pycqa/flake8: 7.1.0 → 7.1.1](PyCQA/flake8@7.1.0...7.1.1)
- [github.com/PyCQA/bandit: 1.7.9 → 1.7.10](PyCQA/bandit@1.7.9...1.7.10)
- [github.com/astral-sh/ruff-pre-commit: v0.5.0 → v0.6.9](astral-sh/ruff-pre-commit@v0.5.0...v0.6.9)
@fyliu fyliu force-pushed the pre-commit-ci-update-config branch from f152f01 to a32ec29 Compare October 17, 2024 21:02
@fyliu
Copy link
Member

fyliu commented Oct 17, 2024

Looks like pre-commit.ci wants us to be using the 4.0 version rather than our current 3.x version. But when I tried to commit the config changes, it fails pre-commit checks because it's using the 3.x .

  • figure out a way to upgrade the pre-commit version being used by git ci

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: PR Needs review (automated column, do not place items here manually)
Development

Successfully merging this pull request may close these issues.

1 participant