be able to set a maximum Zig version for a package

[nektro]

[nektro]

on second thought, does this make sense?

[hqnna]

if a newer tag/release introduces a breaking change, a maximum would prevent someone from trying to build with a broken version.

[nektro]

but why would they commit a max rather than make the fix and commit a new minimum?

[hqnna]

well i mean take river for example, it's built on a specific tag each release, if you're trying to build say a older tag of it, then it'll break with a newer version, but that's just an example i guess.