Skip to content
Snippets Groups Projects
  1. Jul 09, 2021
  2. May 11, 2020
  3. Jan 24, 2019
    • erwan's avatar
      Automate version numbering using Semantic Versionning (semantic-release-gitlab) · 9beabcb2
      erwan authored
      https://www.npmjs.com/package/semantic-release-gitlab
      
      from https://semver.org/ :
        Given a version number MAJOR.MINOR.PATCH, increment the:
      
        - MAJOR version when you make incompatible API changes,
        - MINOR version when you add functionality in a backwards-compatible manner, and
        - PATCH version when you make backwards-compatible bug fixes.
      
      For MAJOR, choosing 6 is obvious.
      
      From Minor it's not clear. This number is supposed to reflect the number of
      add functuionnality, so starting at 0 is not great.
      
      The current version is 1.762, but starting at 762 would be wrong too,
      as most do not deals with new functionnalyties.
      
      In a ideal word, I should use the log and tag every commit tha deals with a new
      functionnalyty, but there is a lot of commits (762).
      
      Hence I,'ve decided to choose 100.
      6.100.1
      9beabcb2
Loading