v1.11 Auto Mode

[miniscruff]

v1.11 brings with it a new feature, "auto mode" #439. To take advantage of this feature you can update your configuration to include what level of bumping ( major, minor or patch ) each kind should use. Then instead of saying changie batch major/minor/patch you can just use changie batch auto.

If you are starting a new project, init will come defaulted with values for the predefined kinds.
Changie itself is using this new feature already, the config can be seen here as always.

Specifically the new options are part of kinds:

kinds:
  - label: Added
    auto: minor
  - label: Changed
    auto: major
  - label: Deprecated
    auto: patch
  - label: Removed
    auto: major
  - label: Fixed
    auto: patch
  - label: Security
    auto: patch

Here is the documentation for the new configuration: https://changie.dev/config/#kindconfig-auto
If you find any issues with this new feature, create an issue.

Note: Auto is also supported in changie next so you could output what the next version would be, if you were to batch auto.
Documentation may not be fully fleshed out at the moment so reach out if there is any confusion as it is improved over time.

[llaville]

This new feature is awesome and solve my GitHub Action Workflows complexity configuration. Thanks a lot !

[llaville]

Love especially the next auto ability

[llaville]

@miniscruff Don't forget to update the Quick Start and Upgrade guides to highlight this new cool feature.

[miniscruff]

Well the upgrade guide is only for things that are backwards incompatible, this feature is completely compatible with the previous version. The quick start could use an update though.

[miniscruff]

Ok, just a small mention on auto mode now in the quick start.

[sheldonhull]

I want to use this feature, but I haven't. I think the main reason is it's easy to result in numeric gaps that are confusing.

For example, if you have five changes that could result in a jump of five patch versions.

If the logic instead was increment, the highest kind of semver jump found in the unreleased changes then I'd use it. Otherwise, a weeks worth of patches would result in lots of semver gaps that would be confusing.

[miniscruff]

The logic is that when you run changie batch it will find the highest semver bump and bump that only. It won't bump N times for N patches. There should not ever be any numeric gaps when using auto mode.
For example:
Before: v1.0.3 with 3 patch updates -> v1.0.4
With 3 patch updates and 1 minor update -> v1.1.0

[miniscruff]

@sheldonhull were you ever able to switch to auto mode or give it a try?

[sheldonhull]

Works like a charm! Exactly how I'd have wanted to design it. Props to you and thank you again!