`auto-update` updates typos from `v1.40.0` to `typos-dict-v0.13.13`

[vidonnus]

Summary

When running prek auto-update for the https://github.com/crate-ci/typos pre-commit, prek updates version v1.40.0 to typos-dict-v0.13.13, a component-scoped tag.

Platform

macOS 15 arm64

Version

prek 0.2.23

.pre-commit-config.yaml

  - repo: https://github.com/crate-ci/typos
    rev: v1.40.0
    hooks:
      - id: typos

Log file

prek auto-update --repo https://github.com/crate-ci/typos -vvv

2025-12-23T04:15:31.709485Z DEBUG prek: 0.2.23
2025-12-23T04:15:31.709551Z DEBUG Args: ["prek", "auto-update", "--repo", "https://github.com/crate-ci/typos", "-vvv"]
2025-12-23T04:15:31.714362Z TRACE get_root: close time.busy=4.76ms time.idle=2.00µs
2025-12-23T04:15:31.714395Z DEBUG Git root: /Users/vidonnus/united/tf-aws-sec-conformance
2025-12-23T04:15:31.714413Z DEBUG Found workspace root at `/Users/vidonnus/united/tf-aws-sec-conformance`
2025-12-23T04:15:31.714432Z DEBUG discover{root="/Users/vidonnus/united/tf-aws-sec-conformance" config=None refresh=true}: Performing fresh workspace discovery
2025-12-23T04:15:31.714470Z TRACE discover{root="/Users/vidonnus/united/tf-aws-sec-conformance" config=None refresh=true}:list_submodules{git_root="/Users/vidonnus/united/tf-aws-sec-conformance"}: close time.busy=5.54µs time.idle=334ns
2025-12-23T04:15:31.716285Z DEBUG Loading project configuration path=.pre-commit-config.yaml
2025-12-23T04:15:31.716885Z TRACE read_config{path="/Users/vidonnus/united/tf-aws-sec-conformance/.pre-commit-config.yaml"}: close time.busy=580µs time.idle=1.12µs
2025-12-23T04:15:31.720198Z TRACE discover{root="/Users/vidonnus/united/tf-aws-sec-conformance" config=None refresh=true}: close time.busy=5.77ms time.idle=500ns
2025-12-23T04:15:31.720385Z TRACE Cloning repository `https://github.com/crate-ci/typos` to `/var/folders/dh/g0ktvljn31q2gx0zgyzlvm0m0000gn/T/.tmpnYjg9g`
2025-12-23T04:15:31.720420Z TRACE Executing `/opt/homebrew/bin/git -c init.defaultObjectFormat= init --template= /var/folders/dh/g0ktvljn31q2gx0zgyzlvm0m0000gn/T/.tmpnYjg9g`
2025-12-23T04:15:31.728114Z TRACE Executing `cd /var/folders/dh/g0ktvljn31q2gx0zgyzlvm0m0000gn/T/.tmpnYjg9g && /opt/homebrew/bin/git remote add origin https://github.com/crate-ci/typos`
2025-12-23T04:15:31.733025Z TRACE Executing `cd /var/folders/dh/g0ktvljn31q2gx0zgyzlvm0m0000gn/T/.tmpnYjg9g && /opt/homebrew/bin/git config extensions.partialClone true`
2025-12-23T04:15:31.736771Z TRACE Executing `cd /var/folders/dh/g0ktvljn31q2gx0zgyzlvm0m0000gn/T/.tmpnYjg9g && /opt/homebrew/bin/git fetch origin HEAD --quiet --filter=blob:none --tags`
2025-12-23T04:15:32.680737Z TRACE Executing `cd /var/folders/dh/g0ktvljn31q2gx0zgyzlvm0m0000gn/T/.tmpnYjg9g && /opt/homebrew/bin/git for-each-ref --sort=-creatordate --format=%(refname:lstrip=2) %(creatordate:unix) refs/tags`
2025-12-23T04:15:32.691043Z DEBUG Using tag `typos-dict-v0.13.13` cutoff timestamp 1766197911
2025-12-23T04:15:32.691062Z TRACE Executing `cd /var/folders/dh/g0ktvljn31q2gx0zgyzlvm0m0000gn/T/.tmpnYjg9g && /opt/homebrew/bin/git tag --points-at typos-dict-v0.13.13^{}`
2025-12-23T04:15:32.700599Z DEBUG Using best candidate tag `typos-dict-v0.13.13` for revision `typos-dict-v0.13.13`
2025-12-23T04:15:32.700621Z TRACE Executing `cd /var/folders/dh/g0ktvljn31q2gx0zgyzlvm0m0000gn/T/.tmpnYjg9g && /opt/homebrew/bin/git checkout --quiet typos-dict-v0.13.13 -- .pre-commit-hooks.yaml`
[https://github.com/crate-ci/typos] updating v1.40.0 -> typos-dict-v0.13.13

[j178]

Related #628, crate-ci/typos#390

[j178]

This is expected behavior for now. typos-dict-v0.13.13 is currently the latest tag in https://github.com/crate-ci/typos. In #719, prek improves the logic so that if both v1.40.1 and typos-dict-v0.13.13 point to the same commit, it will prefer v1.40.1. But since the newest tag right now is just typos-dict-v0.13.13, that’s the only option prek can pick.

I’m thinking about adding some kind of tag filter for repos, like prek auto-update --match "v\d+\.\d+\.\d+", so it only selects tags that match that regex.

[vidonnus]

Another option would be to use the GitHub / GitLab API and hit the releases/latest endpoint. At least in the case of crate-ci/typos, these component versions are not "released".

FWIW, I prefer the current approach. Just figured it was worth mentioning.