Beta tags and commit hashes don't work

[fregante]

The readme states:

pre-commit/README.md

Lines 23 to 24 in 3957a81

	- repo: https://github.com/biomejs/pre-commit
	rev: v1.9.4 # Use the sha / tag you want to point at

But I'm unable to use it

Tag

https://github.com/biomejs/biome/releases/tag/cli%2Fv1.9.5-nightly.81fdedb

  - repo: https://github.com/biomejs/pre-commit
    rev: cli/v1.9.5-nightly.81fdedb

[INFO] Initializing environment for https://github.com/biomejs/pre-commit.
An unexpected error has occurred: CalledProcessError: command: ('/usr/bin/git', 'checkout', 'cli/v1.9.5-nightly.81fdedb')
return code: 1
stdout: (none)
stderr:
    error: pathspec 'cli/v1.9.5-nightly.81fdedb' did not match any file(s) known to git

Hash

https://github.com/biomejs/biome/tree/81fdedb

  - repo: https://github.com/biomejs/pre-commit
    rev: 81fdedb

[INFO] Initializing environment for https://github.com/biomejs/pre-commit.
An unexpected error has occurred: CalledProcessError: command: ('/usr/bin/git', 'checkout', '81fdedb')
return code: 1
stdout: (none)
stderr:
    error: pathspec '81fdedb' did not match any file(s) known to git

[fregante]

v2.0.0-beta.1 works now that it exists, but I think that either the docs need to be updated or the handling of rev needs to be fixed to support hashes, etc

[grst]

I would rather not have beta releases of biomejs/pre-commit. This is because the pre-commit autoupdate service always updates to the latest tag without making any effort to parse the version. This means every repo relying on that service will get pull requests updating to beta tags instead of the latest stable version, e.g. scverse/anndata-plot#10 (comment)

CC @flying-sheep

[flying-sheep]

An alternative would be biomejs/biome-vscode#593

Then we could update our pre-commit config to the beta release while everything keeps working. But one of the two is really necessary (both together would be ideal)