Versioning scheme convention

[jcbhmr]

trafficstars

Right now I'm trying to match versions with the latest Typst version (currently 0.10.0 -- current npm package is [email protected]) https://github.com/typst/typst/releases https://www.npmjs.com/package/typst?activeTab=versions

note that there's a X.Y.Z-N where N goes up. idk if that's the "right" way to do it or not? are there other projects that do it better/differently? is there a convention to this? basically I want a four-part semver specific not a three part specifier lol.

Sidenote: should the first 0.11.0 release be [email protected] or [email protected] or [email protected] ?

[jcbhmr]

i think ill do it sorta like debian does https://serverfault.com/questions/604541/debian-packages-version-convention where it's 1.2.3-1 and then 1.2.3-2? that's what im already doing lol.

[jcbhmr]

Actually what if I did more of a "bindings" approach instead of a "redist" approach? https://github.com/semver/semver/issues/352

What about something like this:

• typst-cli: 0.10.0-1 -- holds JUST the binary cli blob, uses 1.2.3-1 versioning like debian. this is a redist
• typst: 1.0.0+0.10.0 -- holds all the magic fancy bindings and types and such. uses 1.2.3+4.5.6 versioning where 4.5.6 is the "underlying lib" of the bindings wrapper 1.2.3? actually it might be better to bump the starting version to like 100 to avoid version confusion. so like 100.2.3+0.10.0