Tag v8.30.1 not an ancestor of master, breaks pre-commit autoupdate

The tag v8.30.1 is on commit 83d9cd684c87d95d656c1458ef04895a7f1cbd8e and this is not reachable from the master branch. So it's a orphaned tag, and this causes issues with pre-commit autoupdate. Pre‑commit only considers tags that are reachable from the default branch. When a tag points to a commit that is not an ancestor of master, pre‑commit treats it as “older” than any reachable tag, even if the version number is higher. That’s why pre-commit autoupdate consistently rewrites v8.30.1 → v8.30.0.

There are 2 possible ways to fix this:

• Do some git history rewriting so that the release is back on the master branch, and then force push. This will make people maintaining forks unhappy.
• Merge tag v8.30.1 into master and release v8.30.2. This is the cleanest and least disruptive fix.