Add automatic minor increase on feature

[bidoubiwa]

When a new feature is added to a project that already has a fist major version, the update of the semver goes the following way:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards compatible manner, and
PATCH version when you make backwards compatible bug fixes.

This does not apply on packages with no major version.

To avoid having to manually update the minor version on new features, this PR adds the automation of the minor increase when using the new-feature label.

Naming of the label

feature 👍

The name feature is based on the following common practices:
GitHub Labels that are logical, colorful and sensible
GitLab suggested labels

Categorize epics, issues, and merge requests using colors and descriptive titles like bug, feature request, or docs.

Take into account that these are two suggested naming. A lot of other articles exists with different suggestion and the first article also invites to use type: in front of the label.

new-feature 🎉

Another possibility would be to use new-feature as it is more explicit linked to a PR and not an issue.

I suggest new-feature instead of new feature for consistency with breaking-changes and skip-changelog

If you prefer feature 👍
If you prefer new-feature 🎉

⚠️ Wait for this pr before merging

[curquiza]

Awesome! thanks!
I've just added the new-feature label to this repository! :)

[bidoubiwa]

bors merge

[bors]

Build succeeded:

• linter-check
• Tests (Node.js 12)
• Tests (Node.js 14)