Post AlBaaj4gfxpTrRyTJ2 by susie@blob.cat
 (DIR) More posts by susie@blob.cat
 (DIR) Post #AlBaaiLfNLohbouW8G by nicd@social.ahlcode.fi
       2024-08-21T07:22:53.692Z
       
       0 likes, 0 repeats
       
       Days since a v0.x library has broken environments that rely on SemVer: 0.Don't do zero-versioning, please. If you intend to use SemVer, use SemVer. I don't mind if your 1.0.0 quickly turns into 2.0.0 and 3.0.0 since the design was finished. I do mind when my environment breaks because a function was removed in a minor bump in a zero-ver dependency.#SemVer
       
 (DIR) Post #AlBaaj4gfxpTrRyTJ2 by susie@blob.cat
       2024-08-21T08:23:19.474432Z
       
       0 likes, 0 repeats
       
       @nicd Function or feature changes/removals should only happen in major versions imo. Point releases should be small updates (addition no removal) and point point releases only fixes.It's annoying no one follows that lol
       
 (DIR) Post #AlBd3YwVcnlEkB1k9o by nicd@social.ahlcode.fi
       2024-08-21T08:41:26.123Z
       
       1 likes, 0 repeats
       
       @susie@blob.cat That's not just an "imo", it's the SemVer spec (https://semver.org). :) But SemVer also defines 0.x.y as "all bets are off", which was a mistake. There's no safe way to use zero-versions.
       
 (DIR) Post #AlBdAkKfg0V25ykp6G by susie@blob.cat
       2024-08-21T08:52:16.629402Z
       
       0 likes, 0 repeats
       
       @nicd Oh. I wasn't even aware it had a term for it lol That's just "common sense" versioning to me.