How can I trigger a release only by a specified scope?

[gary-Shen]

fix: something should not trigger a release, But fix(scope): something should be. Not only the release notes, But the commit analyzer.

I added a scope field in releaseRules and it didn't work.

Did I miss something?

[travi]

Both of those examples will result in a release under normal circumstances. Are you receiving an error?

[gary-Shen]

Thanks for replying. And no there are no errors. Are there any relevant examples for my scenario?

{
    "repositoryUrl": "https://github.com/gary-Shen/release-test.git",
    "tagFormat": "s3-browser@v${version}",
    "branches": [
      "main"
    ],
    "plugins": [
      ["@semantic-release/commit-analyzer", {
        "preset": "conventionalcommits",
        "releaseRules": [
          {"type": "feat", "release": "minor", "scope": "s3-browser"},
          {"type": "fix", "release": "patch", "scope": "s3-browser"},
          {"type": "perf", "release": "patch", "scope": "s3-browser"},
          {"type": "revert", "release": "patch", "scope": "s3-browser"},
          {"type": "docs", "release": "patch", "scope": "s3-browser"},
          {"type": "style", "release": "patch", "scope": "s3-browser"},
          {"type": "refactor", "release": "patch", "scope": "s3-browser"}
        ]
      }],
      ["@semantic-release/release-notes-generator", {
        "preset": "conventionalcommits",
        "presetConfig": {
            "types": [
                {
                    "type": "fix",
                    "scope": "s3-browser",
                    "hidden": false,
                    "section": "Bug fixes"
                },
                {
                    "type": "feat",
                    "scope": "s3-browser",
                    "hidden": false,
                    "section": "Features"
                },
                {
                    "type": "refactor",
                    "scope": "s3-browser",
                    "hidden": false,
                    "section": "Code Refactoring"
                }
            ]
        }
      }],
      ["@semantic-release/github"]
    ]
  }

For more context information: release-test

Thanks again.

[travi]

The preset you have chosen does not prevent releases when a scope is not provided. Doing so would go beyond what conventional changelog presents typically enable. To understand your options, you need to investigate what your preset enables. Semantic-release simply uses those presets.

[gary-Shen]

Well, I debugged for a while. and found out that the commit analyzer will use the default rules if custom rules does not match any release type.

I'm using a shortcut to solve my needs.

https://github.com/semantic-release/commit-analyzer/blob/master/index.js#L56

- if (isUndefined(commitReleaseType)) {
+ if (isUndefined(commitReleaseType) && !releaseRules) {

It works anyway.
Thanks.