Update pre-commit dependencies #16465
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
| # Various third party dependencies uses `typ` as struct field names (e.g., lsp_types::LogMessageParams) | ||
| "typ", | ||
| # TODO: Remove this once the `TYP` redirects are removed from `rule_redirects.rs` | ||
| "TYP", |
There was a problem hiding this comment.
We could change CFormatErrorType to use CFormatErrorKind and use kind field instead but I've avoided that for now as typ still needs to be ignored because it's used in third-party dependencies. TYP should be removed once the redirect is removed.
There was a problem hiding this comment.
I think I'm going to wait before merging this PR as this is an upstream crate and I'm not sure what's the process of updating it is. I could upstream this change (rust-lang/annotate-snippets-rs#182). cc @BurntSushi
There was a problem hiding this comment.
I think I'm going to merge this, I've opened a PR to update this upstream as well. Happy to make any changes in a follow-up as needed.
There was a problem hiding this comment.
I think this change is fine, but in general the idea is to minimize the diff between our code and upstream as much as possible. That way, if we want to bring in patches from upstream, it's less of a hassle.
I don't know how long this will last or if it's a viable long term strategy, but it's what has been guiding my changes to our vendored copy so far. e.g., There's a lot of other stuff I would want to change too and general code clean-up and what not, but specifically decided against it to keep the diff minimal.
There was a problem hiding this comment.
Thanks, that makes sense, I'll keep that in mind. The upstream PR is merged, so this shouldn't result in any diff.
|
This PR contains the following updates:
v0.9.6->v0.9.9v1.29.7->v1.30.00.31.1->0.31.2v3.5.1->v3.5.2v1.3.1->v1.4.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Note: The
pre-commitmanager in Renovate is not supported by thepre-commitmaintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.Release Notes
astral-sh/ruff-pre-commit (astral-sh/ruff-pre-commit)
v0.9.9Compare Source
See: https://github.com/astral-sh/ruff/releases/tag/0.9.9
v0.9.8Compare Source
See: https://github.com/astral-sh/ruff/releases/tag/0.9.8
v0.9.7Compare Source
See: https://github.com/astral-sh/ruff/releases/tag/0.9.7
crate-ci/typos (crate-ci/typos)
v1.30.0Compare Source
[1.30.0] - 2025-03-01
Features
v1.29.10Compare Source
[1.29.10] - 2025-02-25
Fixes
contaminentascontaminantv1.29.9Compare Source
[1.29.9] - 2025-02-20
Fixes
v1.29.8Compare Source
[1.29.8] - 2025-02-19
Features
python-jsonschema/check-jsonschema (python-jsonschema/check-jsonschema)
v0.31.2Compare Source
woodpecker-ci (2025-02-19)
rbubley/mirrors-prettier (rbubley/mirrors-prettier)
v3.5.2Compare Source
woodruffw/zizmor-pre-commit (woodruffw/zizmor-pre-commit)
v1.4.1Compare Source
See: https://github.com/woodruffw/zizmor/releases/tag/v1.4.1
v1.4.0Compare Source
See: https://github.com/woodruffw/zizmor/releases/tag/v1.4.0
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.