last github releases are heavily outdated

[ssbarnea]

Last releases are more than an year old while new versions were "released" only by tagging, without a gihub release.

This confuses any github visitor into believing that last release was very old. It also have implication on other tooling like dependabot or renovate.

Best it would be to make use of github releases, but if that is not possible, unpublishing the releases and hiding the release sidebar would ease the confusion a little bit.

[ematipico]

Best it would be to make use of github releases, but if that is not possible, unpublishing the releases and hiding the release sidebar would ease the confusion a little bit.

I really don't what you mean

[flying-sheep]

This:

[ematipico]

I see what you mean now. Feel free to send a PR :)

[echoix]

I see what you mean now. Feel free to send a PR :)

I don't think outside contributors can make PRs to manage releases on GitHub, it's something that maintainer (or even more) permission level in the repo can do.

[ematipico]

The idea is to automate them via CI

[fregante]

You could alternatively delete all releases so that GitHub only shows tags. They're kinda redundant if they match Biome's tags anyway.

[dmyersturnbull]

This just really tripped me up: I saw v2.3.6 in my .pre-commit-config.yaml, figured I'd made a mistake, and tried to downgrade to v0.6.1 before realizing what happened.

I sometimes simply ignore repos / decide not to use them if their last GitHub Release is old. I don't normally think to check for tags, too.

Anyway, deleting all the GitHub Releases sounds like a good solution.

[Guiorgy]

[...] tried to downgrade to v0.6.1 before realizing what happened.

Yep, I got jebaited by GitHub Releases too :P.