home.social

#semanticversioning — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #semanticversioning, aggregated by home.social.

  1. The failure of #SemanticVersioning is that, once a project/library reaches some degree of mature popularity, nobody ever wants to bump the first digit. They'll find endless excuses not to.

    So if your project got really established at version 1.1, it'll be version 1.something forever.

    Like many geeky technical things, SV's an elegant solution that completely fails to account for how people behave.

  2. The failure of #SemanticVersioning is that, once a project/library reaches some degree of mature popularity, nobody ever wants to bump the first digit. They'll find endless excuses not to.

    So if your project got really established at version 1.1, it'll be version 1.something forever.

    Like many geeky technical things, SV's an elegant solution that completely fails to account for how people behave.

  3. The failure of #SemanticVersioning is that, once a project/library reaches some degree of mature popularity, nobody ever wants to bump the first digit. They'll find endless excuses not to.

    So if your project got really established at version 1.1, it'll be version 1.something forever.

    Like many geeky technical things, SV's an elegant solution that completely fails to account for how people behave.

  4. The failure of #SemanticVersioning is that, once a project/library reaches some degree of mature popularity, nobody ever wants to bump the first digit. They'll find endless excuses not to.

    So if your project got really established at version 1.1, it'll be version 1.something forever.

    Like many geeky technical things, SV's an elegant solution that completely fails to account for how people behave.

  5. The failure of #SemanticVersioning is that, once a project/library reaches some degree of mature popularity, nobody ever wants to bump the first digit. They'll find endless excuses not to.

    So if your project got really established at version 1.1, it'll be version 1.something forever.

    Like many geeky technical things, SV's an elegant solution that completely fails to account for how people behave.

  6. 📰 bump というバージョンバンプツールを作った (👍 35)

    🇬🇧 Created 'bump': a universal version bumping tool supporting multiple languages (Go, Rust, Python, etc.) with semantic versioning. Inspired by gobump.
    🇰🇷 'bump' 개발: Go, Rust, Python 등 여러 언어를 지원하는 범용 버전 범핑 도구. 시맨틱 버저닝 적용. gobump에서 영감을 받음.

    🔗 zenn.dev/mattn/articles/28ff86

    #DevTools #SemanticVersioning #CLI #Zenn

  7. 📰 bump というバージョンバンプツールを作った (👍 35)

    🇬🇧 Created 'bump': a universal version bumping tool supporting multiple languages (Go, Rust, Python, etc.) with semantic versioning. Inspired by gobump.
    🇰🇷 'bump' 개발: Go, Rust, Python 등 여러 언어를 지원하는 범용 버전 범핑 도구. 시맨틱 버저닝 적용. gobump에서 영감을 받음.

    🔗 zenn.dev/mattn/articles/28ff86

    #DevTools #SemanticVersioning #CLI #Zenn

  8. 📰 bump というバージョンバンプツールを作った (👍 35)

    🇬🇧 Created 'bump': a universal version bumping tool supporting multiple languages (Go, Rust, Python, etc.) with semantic versioning. Inspired by gobump.
    🇰🇷 'bump' 개발: Go, Rust, Python 등 여러 언어를 지원하는 범용 버전 범핑 도구. 시맨틱 버저닝 적용. gobump에서 영감을 받음.

    🔗 zenn.dev/mattn/articles/28ff86

    #DevTools #SemanticVersioning #CLI #Zenn

  9. 📰 bump というバージョンバンプツールを作った (👍 35)

    🇬🇧 Created 'bump': a universal version bumping tool supporting multiple languages (Go, Rust, Python, etc.) with semantic versioning. Inspired by gobump.
    🇰🇷 'bump' 개발: Go, Rust, Python 등 여러 언어를 지원하는 범용 버전 범핑 도구. 시맨틱 버저닝 적용. gobump에서 영감을 받음.

    🔗 zenn.dev/mattn/articles/28ff86

    #DevTools #SemanticVersioning #CLI #Zenn

  10. 📰 bump というバージョンバンプツールを作った (👍 35)

    🇬🇧 Created 'bump': a universal version bumping tool supporting multiple languages (Go, Rust, Python, etc.) with semantic versioning. Inspired by gobump.
    🇰🇷 'bump' 개발: Go, Rust, Python 등 여러 언어를 지원하는 범용 버전 범핑 도구. 시맨틱 버저닝 적용. gobump에서 영감을 받음.

    🔗 zenn.dev/mattn/articles/28ff86

    #DevTools #SemanticVersioning #CLI #Zenn

  11. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  12. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  13. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  14. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  15. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  16. Convention over customization.
    This is why I love projects like Keep a Changelog, Conventional Commits and Semantic Versioning. They allow for some neat processing by other tools which just wouldn't ever be possible if everyone did their own, custom thing.

    #git #ConventionalCommits #SemanticVersioning #Neovim #NeovimLazy

  17. Übrigens bemerkenswerte Begründung seitens #Apple: „Das Update zu 13.5.1 ist noch so neu, dass man über Nebenwirkungen noch nichts wissen kann.“
    Na, das ist mal ein Argument. Nach einer Debatte über #SemanticVersioning und #BreakingChanges haben sie es immerhin in ihren Tracker eingefüttert. Meine Ankündigung, darüber zu bloggen, dass #MacOS bei jedem Update #DisplayPort over #USB kaputtmacht, war dann auch ein Argument.

  18. Une proposition intéressante d'ajouter une notion supplémentaire au *Semantic Versioning* pour distinguer les "simples" breaking changes des changements plus conséquents.

    L'intérêt de cette approche est qu'elle reste compatible avec le semantic versionning lui-même.

    🔗 antfu.me/posts/epoch-semver

    #version #SemanticVersioning

  19. Convention over customization.
    This is why I love projects like Keep a Changelog, Conventional Commits and Semantic Versioning. They allow for some neat processing by other tools which just wouldn't ever be possible if everyone did their own, custom thing.

  20. @parcifal not silly question at all!

    you can add a plugin to your repo and let it version it for you.

    Check Semantic Versioning, I found this post about it that could be helpful.

    hodgkins.io/automating-semanti

    It is for nodejs apps, but I think you can find similar plugins/bots for other languages as well

    #programming #semanticVersioning #code #nodejs

  21. In this #InfoQ article, Ashwin Raghav addresses the most contentious parts of the #SemVer (#SemanticVersioning) standard to understand how you can trade off backward compatibility and upgradability with modernization and iterability: bit.ly/3U6gKbF

    #CloudComputing #API #SaaS

  22. When I forked @[email protected] `snap-pac` into `apk-snap` I just kept going with `snap-pac`'s release numbers. i.e. I started from v3.0.2. The fork is now at 3.1.0. After thinking about it, maybe I should've started at 0.0.1🤔

    What do you think?

    #AlpineLinux #development #dev #SemanticVersioning #SemVer #forkingSoftware

  23. @delfuego @TomSellers @electronjs @getpostman Some of those numbers are deceptively lower than the current supported #Electron releases: electronjs.org/docs/latest/tut
    But they all include Electron versions released in the past 18 months.

    Like a lot of #JavaScript apps, Electron iterates versions *really* fast. #SemanticVersioning is *not* a guide to the chronological age of software, only its compatibility with *other* software.

  24. What the heck, Microsoft? TIL that the "Windows Subsystem for Linux" (WSL), which moved from WSL 1 to WSL 2 is actually separately versioned. So the current WSL 2 release is 1.2.5.

    WSL 2 1.2.5

    And the current pre-release tag is WSL 2 2.0.0

    I mean, they could have made it *somewhat *less confusing by calling it WSL2 instead of WSL 2 but, nope.

    Or, they could have called it WSL 2.0.0 when they moved from WSL 1 but, nope.

    🤪

    #SemanticVersioning #MicrosoftVersioning #NeerTheTwainShallMeet

  25. Curious to hear from folks who actually practice semantic versioning for documents about your workflow + how you think about the process.

    More background here: semverdoc.org/

    And a helpful post w/ an alternate (more human readable) versioning convention here: ulrich-anders.eu/blog/semantic

    #SemanticVersioning #Documentation

  26. Would adding a new translation to your software count as a minor or patch bump on ? 🤔

  27. Semantic versioning using emojies:

    😱 .🤗 .🤒

    Thanks to @mpdude and @sebastian for sharing 😃

    #devlife #semanticversioning

  28. Une proposition intéressante d'ajouter une notion supplémentaire au *Semantic Versioning* pour distinguer les "simples" breaking changes des changements plus conséquents.

    L'intérêt de cette approche est qu'elle reste compatible avec le semantic versionning lui-même.

    🔗 antfu.me/posts/epoch-semver

    #version #SemanticVersioning

  29. Une proposition intéressante d'ajouter une notion supplémentaire au *Semantic Versioning* pour distinguer les "simples" breaking changes des changements plus conséquents.

    L'intérêt de cette approche est qu'elle reste compatible avec le semantic versionning lui-même.

    🔗 antfu.me/posts/epoch-semver

    #version #SemanticVersioning