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

MAINT: pre-commit autoupdate 2024-07-31 #651

Merged
merged 1 commit into from
Aug 2, 2024

Conversation

cclauss
Copy link
Contributor

@cclauss cclauss commented Jul 31, 2024

Perform a periodic update of the tools in pre-commit.

% pre-commit install

pre-commit installed at .git/hooks/pre-commit

% pre-commit autoupdate

[https://github.com/pre-commit/pre-commit-hooks] updating v4.5.0 -> v4.6.0
[https://github.com/astral-sh/ruff-pre-commit] updating v0.1.5 -> v0.5.5
[https://github.com/fsfe/reuse-tool] updating v2.1.0 -> v4.0.3

% pre-commit run --all-files

[ ... ]
ruff.....................................................................Failed
- hook id: ruff
- files were modified by this hook

warning: The top-level linter settings are deprecated in favour of their counterparts in the `lint` section. Please update the following options in `pyproject.toml`:
  - 'extend-ignore' -> 'lint.extend-ignore'
  - 'select' -> 'lint.select'

Fixed 1 error:
- tests/test_editable.py:
    1 × RUF100 (unused-noqa)

Found 1 error (1 fixed, 0 remaining).
  • Manually edited pyproject.toml to add lint. in two places to match ruff's new syntax.

@rgommers rgommers added the maintenance Regular code improvements that are not new features nor end-user-visible bugs label Aug 2, 2024
@rgommers rgommers changed the title pre-commit autoupdate 2024-07-31 MAINT: pre-commit autoupdate 2024-07-31 Aug 2, 2024
Copy link
Contributor

@rgommers rgommers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @cclauss, this update looks good to me.

Note that we tend to not merge the auto-generated PRs like gh-543, because they come way to quickly. If you'd be interested in reconfiguring that so they don't come more than once every 2 or 3 months, it'll be easier to merge them as they come in without completely clogging up the commit history.

@rgommers rgommers added this to the v0.17.0 milestone Aug 2, 2024
@rgommers rgommers merged commit 9df4ffd into mesonbuild:main Aug 2, 2024
35 of 39 checks passed
@cclauss cclauss deleted the pre-commit_autoupdate_2024-07-31 branch August 2, 2024 09:09
cclauss added a commit to cclauss/meson-python that referenced this pull request Aug 2, 2024
rgommers pushed a commit that referenced this pull request Aug 2, 2024
@rgommers rgommers mentioned this pull request Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Regular code improvements that are not new features nor end-user-visible bugs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants