• webbureaucrat@floss.social
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    1 year ago

    @sugar_in_your_tea If you’re interested, I recommend looking at how Elm does it. Elm has automatic semver enforcement in its package system.

    The long and the short is
    missing stuff: major change
    new stuff: minor change
    patch: internal implementation change.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I gave a more thorough response with examples to the other user that replied (link on my instance here, but basically there are cases where you could break someone’s code with a patch release.

      I’m completely fine with using tools to help decide what versions to assign, but in general developers should not hesitate to increment the major version if there’s any doubt.