Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: preserve major version zero on breaking changes (when using conventional commits) #2486

Merged
merged 1 commit into from May 24, 2020
Merged

feat: preserve major version zero on breaking changes (when using conventional commits) #2486

merged 1 commit into from May 24, 2020

Commits on Mar 9, 2020

  1. feat: preserve major version zero on breaking changes

    According to semver, major version zero (0.y.z) is for initial
    development. Anything MAY change at any time. The public API
    SHOULD NOT be considered stable. The version 1.0.0 defines
    the (initial stable) public API.
    
    To allow monorepos to use major version zero meaningfully,
    the transition from 0.x to 1.x must be explicitly requested
    by the user. Breaking changes MUST NOT automatically bump
    the major version from 0.x to 1.x.
    
    The usual convention is to use semver-patch bumps for bugfix
    releases and semver-minor for everything else, including
    breaking changes. This matches the behavior of `^` operator
    as implemented by `npm`.
    
    This commit implements the convention described above:
    - a patch-level change bumps semver-patch version (NO CHANGE)
    - a minor-level change bumps semver-minor version (NO CHANGE)
    - a major-level (breaking) change bumps semver-minor version (NEW)
    
    Signed-off-by: Miroslav Bajtoš <mbajtoss@gmail.com>
    bajtos committed Mar 9, 2020
    Copy the full SHA
    398733e View commit details
    Browse the repository at this point in the history