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.

Sign up for GitHub

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

Jump to bottom

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

Open
depressedPlumber502 opened this issue Jan 21, 2025 · 0 comments
Open

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

depressedPlumber502 opened this issue Jan 21, 2025 · 0 comments

Comments

@depressedPlumber502
Copy link

depressedPlumber502 commented Jan 21, 2025 •
edited
Loading

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@depressedPlumber502