Skip to content

How to make sure NO Major release is triggered? #750

@depressedPlumber502

Description

@depressedPlumber502

Hello!

I need to make sure that whatever commit message is there won't be a MAJOR release.

Currently with default angular preset all that is needed is BREAKING CHANGE: in the commit message footer to trigger a MAJOR release.

For now I just associate breaking changes with a minor release which is fine for our use case and it results in just a MINOR version upgrade.

  plugins: [
    [
      "@semantic-release/commit-analyzer",
      { releaseRules: [{ breaking: true, release: "minor" }] },
    ],
  ],

Question - is there a more correct solution ?

Thank you

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions