Post

Proposing an extended SemVer - 🗿 Epoch Semantic Versioning to communicate better about versions. Thinking of adopting this to all my projects, and finally eliminating my lousy habit of forever zero-major practice 😜 What do you think? 👀 antfu.me/posts/epoch-...

That's a neat hack on top of SemVer. As a heavy user of semantic-release, I'm wondering how we might denote the jump from 100.x.x to 200.x.x. Semantic commits make it easier to manage smaller version jumps, but incrementally shipping big rewrites like this might be more challenging.

Do the developers you work with understand that “chore” has nothing to do with how they feel about the work involved? Because… most of mine don’t.

It’s a question of education about the tooling (conventional commits) and having the right validation (commitlint) in place as a safety net I guess. gist.github.com/Zekfad/f51cb...

How do you handle this commit? - fix github action ... (x commits later) - F**** U GITHUB ACTION

As long as it’s in a branch/PR, I’m not picky about conventions. The squashed commit needs to follow convco though, and that one erases all the CI ping pong.

But my secret weapon for this is a dedicated repo I can spam with CI experiments: github.com/franky47/act...