How can I set additional releaseRules of the action?

[pawellabaj]

I have dependabot commits in my repo that looks as follow:

build: maven: (deps): bump junit-jupiter.version from 5.10.0 to 5.10.1 (#136)

Bumps `junit-jupiter.version` from 5.10.0 to 5.10.1.
(...)

I want to make them to bump patch number in my release version.

I tried to set following rule with .releaserc.yml or package.json files

[
        "@semantic-release/commit-analyzer",
        {
          "preset": "angular",
          "releaseRules": [
            {
              "type": "build",
              "scope": "deps",
              "release": "patch"
            }
          ]
        }
      ]

It looks that he action is not looking for configuration overriding in these files.

Is it possible to define additional ruleset? How to do this?

[EricCrosson]

Hi @pawellabaj, that sounds a bit outside the scope of this repository. You probably have already seen this, but I believe these docs contain the most relevant information around configuring commit-analyzer rules: https://github.com/semantic-release/commit-analyzer

I'm not too familiar with custom rules, but in your case, I wonder if the "scope": "deps" is what's causing your rule to not match the example commit message. In my head, I'd figure {"type": "build", "scope": "deps"} to match a commit message like:

build(deps): lorem ipsum

Have you tried removing scope from your release rule?

[pawellabaj]

I tried different entries.

It looks that the action uses always the same package.json:

Run : install semantic-release package manifest
  : install semantic-release package manifest
  mkdir -p "$node_workdir"
  cp "/home/runner/work/_actions/semantic-release-action/next-release-version/v4/internal/package.json" "/home/runner/work/_actions/semantic-release-action/next-release-version/v4/internal/package-lock.json" "$node_workdir/"

[EricCrosson]

Oh yeah, you're right. It does appear that the current implementation is fundamentally incapable of supporting release rules:

next-release-version/internal/action.yml

Lines 60 to 67 in dcf34f0

	# Note: do not override the analyze-commits plugin because this affects how
	# semantic-release calculates the next version number!
	#
	# If a user's semantic-release config specifies a custom plugin for
	# analyze-commits, it will not be installed by this plugin and fail.
	#
	# If you're the lucky user who triggers this edge-case, please comment on
	# https://github.com/semantic-release-action/next-release-version/issues/13