Default to patch release

[vishnusraju]

Hi, We in our team are trying to automate release process and would like to set the default commit to have a patch release. Found some few similar issues (Isue 162) and tried the different options. it did not help. Below is the .releaserc.yml used for deploy.

It works fine while following the commit conventions. But all other mesages are pretty much ignored even after updating the file as below:

plugins:
- "@semantic-release/commit-analyzer"
- releaseRules:
  - type: "demo"
    release: patch
  - message: "*"
    release: patch
  - subject: "*"
    release: patch
- "@semantic-release/release-notes-generator"
- - "@semantic-release/exec"
  - verifyReleaseCmd: "echo ${nextRelease.version} > VERSION.txt"
- "@semantic-release/gitlab"

branches:
- "master"
- "+([0-9])?(.{+([0-9]),x}).x"
- name: "alpha"
  prerelease: "alpha"

[travi]

please include output from executing with the debug flag enabled.

- - "@semantic-release/exec"

it is possible that the double - is causing a parsing problem with your config file

[vishnusraju]

Hi, I tried to use json instead of yaml and here is the debug log, So this is the new configuration file:

{
  "plugins": [
    ["@semantic-release/commit-analyzer", {
      "preset": "angular",
      "releaseRules": [
        {"type": "*", "release": "patch"},
        {"subject": "*", "release": "patch"}
      ]
    }],
    "@semantic-release/release-notes-generator"
  ]
}

and here are the logs

C:\Dev\git\nuget-test>npx semantic-release --debug
npx: installed 755 in 37.937s
[8:46:07 AM] [semantic-release] » i  Running semantic-release version 17.3.9
  semantic-release:config load config from: C:\Dev\git\nuget-test\.releaserc.json +0ms
  semantic-release:config options values: {
  semantic-release:config   branches: [
  semantic-release:config     '+([0-9])?(.{+([0-9]),x}).x',
  semantic-release:config     'master',
  semantic-release:config     'next',
  semantic-release:config     'next-major',
  semantic-release:config     { name: 'beta', prerelease: true },
  semantic-release:config     { name: 'alpha', prerelease: true }
  semantic-release:config   ],
  semantic-release:config   repositoryUrl: 'https://gitlab.company.com/remote-diagnostics/tools-and-utilities/nuget-test.git',
  semantic-release:config   tagFormat: 'v${version}',
  semantic-release:config   plugins: [
  semantic-release:config     [ '@semantic-release/commit-analyzer', [Object] ],
  semantic-release:config     '@semantic-release/release-notes-generator'
  semantic-release:config   ],
  semantic-release:config   _: [],
  semantic-release:config   debug: true,
  semantic-release:config   '$0': 'path to semantic-release.js'
  semantic-release:config } +241ms
  semantic-release:plugins options for @semantic-release/commit-analyzer/analyzeCommits: {
  semantic-release:plugins   preset: 'angular',
  semantic-release:plugins   releaseRules: [
  semantic-release:plugins     { type: '*', release: 'patch' },
  semantic-release:plugins     { subject: '*', release: 'patch' }
  semantic-release:plugins   ]
  semantic-release:plugins } +0ms
[8:46:08 AM] [semantic-release] » √  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
  semantic-release:plugins options for @semantic-release/release-notes-generator/generateNotes: {} +15ms
[8:46:08 AM] [semantic-release] » √  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[8:46:08 AM] [semantic-release] » ‼  This run was not triggered in a known CI environment, running in dry-run mode.
  semantic-release:get-git-auth-url Verifying ssh auth by attempting to push to  https://gitlab.company.com/remote-diagnostics/tools-and-utilities/nuget-test.git +0ms
  semantic-release:get-tags found tags for branch master: [ { gitTag: 'v1.0.0', version: '1.0.0', channels: [ null ] }, { gitTag: 'v1.1.0', version: '1.1.0', channels: [ null ] }, { gitTag: 'v1.1.1', version: '1.1.1', channels: [ null ] }, { gitTag: 'v1.2.0', version: '1.2.0', channels: [ null ] }, { gitTag: 'v2.0.0', version: '2.0.0', channels: [ null ] }, { gitTag: 'v2.1.0', version: '2.1.0', channels: [ null ] }, { gitTag: 'v2.1.1', version: '2.1.1', channels: [ null ] }, { gitTag: 'v2.2.0', version: '2.2.0', channels: [ null ] }, { gitTag: 'v2.2.1', version: '2.2.1', channels: [ null ] }, { gitTag: 'v2.3.0', version: '2.3.0', channels: [ null ] }, { gitTag: 'v2.4.0', version: '2.4.0', channels: [ null ] }, { gitTag: 'v2.4.1', version: '2.4.1', channels: [ null ] }, { gitTag: 'v3.0.0', version: '3.0.0', channels: [ null ] }, { gitTag: 'v4.0.0', version: '4.0.0', channels: [ null ] }, { gitTag: 'v4.1.0', version: '4.1.0', channels: [ null ] }, { gitTag: 'v4.1.1', version: '4.1.1', channels: [ null ] }, { gitTag: 'v4.1.2', version: '4.1.2', channels: [ null ] }, { gitTag: 'v4.1.3', version: '4.1.3', channels: [ null ] }, { gitTag: 'v4.1.4', version: '4.1.4', channels: [ null ] }, { gitTag: 'v4.1.5', version: '4.1.5', channels: [ null ] }, { gitTag: 'v4.2.0', version: '4.2.0', channels: [ null ] }, { gitTag: 'v5.0.0', version: '5.0.0', channels: [ null ] }, { gitTag: 'v5.0.1', version: '5.0.1', channels: [ null ] }, { gitTag: 'v5.0.2', version: '5.0.2', channels: [ null ] }, { gitTag: 'v5.0.3', version: '5.0.3', channels: [ null ] }, { gitTag: 'v5.0.4', version: '5.0.4', channels: [ null ] }, { gitTag: 'v5.1.0', version: '5.1.0', channels: [ null ] }, { gitTag: 'v6.0.3', version: '6.0.3', channels: [ null ] }, { gitTag: 'v6.1.0', version: '6.1.0', channels: [ null ] }, { gitTag: 'v7.0.0', version: '7.0.0', channels: [ null ] }, { gitTag: 'v7.0.1', version: '7.0.1', channels: [ null ] } ] +0ms
[9:18:55 AM] [semantic-release] » ‼  Run automated release from branch master on repository https://gitlab.company.com/remote-diagnostics/tools-and-utilities/nuget-test.git in dry-run mode
[9:18:57 AM] [semantic-release] » √  Allowed to push to the Git repository
[9:18:57 AM] [semantic-release] » i  Found git tag v7.0.1 associated with version 7.0.1 on branch master
  semantic-release:get-commits Use from: d28912fe2fa39e5ab96aa22185705ebe5f72a28e +0ms
[9:18:58 AM] [semantic-release] » i  Found 2 commits since last release
  semantic-release:get-commits Parsed commits: [ { commit: { long: '85efb36a7e5f1134b8b776008cdc75edfc960bf6', short: '85efb36' }, tree: { long: '1a1d3b7b1b06e70083327e08e7bbd66a050c717a', short: '1a1d3b7' }, author: { name: 'name', email: 'email', date: 2021-02-25T07:54:46.000Z }, committer: { name: 'name', email: 'email', date: 2021-02-25T07:54:46.000Z }, subject: 'Trying json', body: '', hash: '85efb36a7e5f1134b8b776008cdc75edfc960bf6', committerDate: 2021-02-25T07:54:46.000Z, message: 'Trying json', gitTags: '(HEAD -> master, origin/master)' }, { commit: { long: '05942e6e9475c6dde10ff643371cb9ca62ae4d88', short: '05942e6' }, tree: { long: '2082e6172b0912ac1d576ac458f214098e618862', short: '2082e61' }, author: { name: 'name', email: 'email', date: 2021-02-25T06:45:25.000Z }, committer: { name: 'name', email: 'email', date: 2021-02-25T06:45:25.000Z }, subject: 'Adding debug logs', body: '', hash: '05942e6e9475c6dde10ff643371cb9ca62ae4d88', committerDate: 2021-02-25T06:45:25.000Z, message: 'Adding debug logs', gitTags: '' } ] +185ms
[9:18:58 AM] [semantic-release] » i  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[9:18:58 AM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analyzing commit: Trying json
  semantic-release:commit-analyzer Analyzing with custom rules +0ms
  semantic-release:commit-analyzer Analyzing with default rules +7ms
[9:18:58 AM] [semantic-release] [@semantic-release/commit-analyzer] » i  The commit should not trigger a release
[9:18:58 AM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analyzing commit: Adding debug logs
  semantic-release:commit-analyzer Analyzing with custom rules +1ms
  semantic-release:commit-analyzer Analyzing with default rules +1ms
[9:18:58 AM] [semantic-release] [@semantic-release/commit-analyzer] » i  The commit should not trigger a release
[9:18:58 AM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analysis of 2 commits complete: no release
[9:18:58 AM] [semantic-release] » √  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[9:18:58 AM] [semantic-release] » i  There are no relevant changes, so no new version is released.

[travi]

the contents of your new config are very different from the config that you started with above. from the issue you referenced, semantic-release/commit-analyzer#162 (comment) highlights why tag is unlikely to be what you are looking for. did you try subject or message?

[vishnusraju]

Yeah i thought of reducing the scope and the trying the basic configs first. I did try subjecct and message. It did not work as well.

[macrozone]

i would also like to know how you can configure to fallback ALWAYS to patch release. I think that should have a specific configuration option.

[MeNsaaH]

I was able to get this working using message instead of subject or scope.

      "releaseRules": [
        {"message": "*", "release": "patch"}
      ]

[mstrucken]

Property matching in the releaseRules option utilizes globs. To ensure that you really match everything, use ** instead of *:

      "releaseRules": [
        {"message": "**", "release": "patch"}
      ]

[dgattey]

This only worked for me when I took out "preset": "eslint". I thought I needed the eslint preset to be able to use "message" but I guess not

[ardunster]

Our team tried a variety of different glob patterns in commit-analyzer's releaseRules array, but since we couldn't find any documentation explaining where different values like type, scope, etc come from and what all the possible filters might be to ensure we covered all of them, occasionally things would still slip through the cracks, fail to trigger a release, and break the rest of the deployment pipelines due to not creating and outputting a release version.

I think we finally have a solution using @semantic-release/exec instead, by putting this in the .releaserc plugins array:

    [
      "@semantic-release/exec",
      {
        "analyzeCommitsCmd": "echo patch"
      }
    ],

So far haven't seen whether this works properly with things commit-analyzer tags as minor and major releases, but it definitely did make a release happen that commit-analyzer thought didn't qualify as a release. Hopefully this is helpful to someone!