Version 6.1.0 different outcome for monorepo configuration

[malins]

Hello,

that's my configuration:

remote-name: "origin"
git-name: "Name"
git-email: "no@xyz.com"
tag-prefix: "v"
rules:
  minor:
    - feat
  patch:
    - fix
    - perf
    - revert
branches:
  - name: "main"
monorepo:
  - name: a
    path: ./services/a/
  - name: b
    path: ./services/b/
  - name: c
    path: ./services/c/

Version 6.1.0 is not correctly detecting new releases in services. Version 6.0.1 reports different outcome:

{"level":"info","new-release":false,"version":"0.8.0","branch":"main","project":"a","message":"no new release"}
{"level":"info","new-release":true,"version":"0.13.2","branch":"main","project":"b","message":"dry-run enabled, next release found"}
{"level":"info","new-release":true,"version":"0.12.1","branch":"main","project":"c","message":"dry-run enabled, next release found"}

vs

{"level":"info","new-release":false,"version":"0.8.0","branch":"main","project":"a","message":"no new release"}
{"level":"info","new-release":false,"version":"0.13.1","branch":"main","project":"b","message":"no new release"}
{"level":"info","new-release":false,"version":"0.12.0","branch":"main","project":"c","message":"no new release"}

[s0ders]

Hey @malins , can you link the chain of commit types that should lead to the correct upgrade for each services in your config so that I can try to reproduce the issue and identify where the logic falls short?
e.g.:

• Service A: fix -> fix -> feat
• Service B: feat -> revert -> perf