Default release type of @auto-it/conventional-commits

[hasparus]

I'm not creating an issue, because I may well be just confused here, but shouldn't the defaultReleaseType of @auto-it/conventional-commits be something like "none" or "internal"?

skip-release cancels whole release, even if other merged PRs since the last release are labeled as minor. (https://github.com/intuit/auto/blob/main/packages/core/src/semver.ts#L221-L227)

[hipstersmoothie]

I think to fit with the default auto experience yeah it would make sense to change that. Could you submit a PR?

[hasparus]

Could you submit a PR?

Okay, I gave the rest of the code a brief look. Here are my observations.

The test at conventional-commits.test.ts#L370-L401 actually guards against a similar scenario, but it doesn't catch the case where the user merges one PR with chores only, which is then labeled as skip-release and then a PR with a fix or feature. Since labels from merged PRs since the last release are merged, we end up skipping a release of these fixes.

I fixed the problem for myself by configuring defaultReleaseType to "none", but maybe the problem lies in the logic which decides if the release is skipped based on skip-release labels?

Right now, one skip-release label is enough to skip the whole thing. Shouldn't Auto skip only if all PRs in the release contain the label?