Skip to content

chore(deps): pre-commit.ci autoupdate#16

Merged
cbachhuber merged 4 commits into
mainfrom
pre-commit-ci-update-config
May 10, 2026
Merged

chore(deps): pre-commit.ci autoupdate#16
cbachhuber merged 4 commits into
mainfrom
pre-commit-ci-update-config

Conversation

pre-commit-ci Bot and others added 4 commits May 4, 2026 21:26
updates:
- [github.com/pre-commit/mirrors-clang-format: v22.1.2 → v22.1.4](pre-commit/mirrors-clang-format@v22.1.2...v22.1.4)
- [github.com/hukkin/mdformat: 0.7.22 → 1.0.0](hukkin/mdformat@0.7.22...1.0.0)
- [github.com/crate-ci/typos: v1.39.0 → v1](crate-ci/typos@v1.39.0...v1)
- [github.com/hofbi/dev-tools: 1.8.0 → whoowns-0.8.1](hofbi/dev-tools@1.8.0...whoowns-0.8.1)
@cbachhuber cbachhuber merged commit e463265 into main May 10, 2026
3 checks passed
Comment thread .pre-commit-config.yaml
- id: mdformat
- repo: https://github.com/crate-ci/typos
rev: v1.39.0
rev: v1
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
rev: v1
rev: v1.46.1

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Looking at https://github.com/crate-ci/typos/tree/v1, I got the impression that @epage uses v1 as kind of rolling release that always matches the latest tag. v1 found new typos in this PR, so I might be right. If you don't have evidence for this being different, I'll try v1 and see if my theory is true.

This of course somewhat defeats the purpose of pinning a version to have things under control. Still, I don't see this as a problem (especially in this repo).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants