Skip to content

does not fail when commits message don't follow conventional commits #278

Closed
@electriquo

Description

@electriquo

This is a snippet from my configuration

plugins: [
  ["@semantic-release/commit-analyzer", {
    preset: "conventionalcommits",
  }],
  ["@semantic-release/release-notes-generator", {
    preset: "conventionalcommits",
   }],
  ...

and and logs indicate that it was loaded

semantic-release:plugins options for @semantic-release/commit-analyzer/analyzeCommits: { preset: 'conventionalcommits' }
[semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: foo
semantic-release:commit-analyzer Analyzing with default rules +0ms
[@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[@semantic-release/commit-analyzer] › ℹ  Analysis of 1 commits complete: no release
› ✔  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"

If it matters have installed conventional-changelog-conventionalcommits.

I would expect the plugin to fail semantic release when the git commit message history contains a commit that does not follow conventional commit.

In the documentation it is written

For presets that expects a configuration object, such as conventionalcommits, the presetConfig option must be set.

maybe this is the reason that the plugin does not fail (what should be the presetConfig?).

What am I missing? Is this a bug?

Thank you

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions