fix(deps): update dependency conventional-recommended-bump to v9 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
conventional-recommended-bump (source)	6.1.0 -> 9.0.0

---

Release Notes

conventional-changelog/conventional-changelog (conventional-recommended-bump)

v9.0.0: conventional-recommended-bump: v9.0.0

Compare Source

⚠ BREAKING CHANGES

• git-semver-tags,conventional-recommended-bump: gitSemverTags and conventionalRecommendedBump now return promises
• standard-changelog: createIfMissing method now returns a promise

Features

• git-semver-tags,conventional-recommended-bump: refactoring to use promises instead of callbacks (#​1112) (1697ecd)
• standard-changelog: use promises (#​1111) (5015ab7)

Bug Fixes

• conventional-changelog-conventionalcommits: fix handling input params (#​1120) (e721cde)

v8.0.0: conventional-recommended-bump: v8.0.0

Compare Source

⚠ BREAKING CHANGES

• Node >= 16 is required
• Now all presets are exports preset config factory function. conventional-changelog-preset-loader now exports new loadPreset and createPresetLoader functions. If you are using presets indirectly, using preset name, no any changes in configuration needed, just upgrade packages to latest versions.

Features

• drop node 14 support (#​1085) (1bce036)
• git-semver-tags,conventional-recommended-bump: define skip-unstable option in cli (#​1066) (0ffec3f)
• unified presets interface (#​1045) (8d0ffbe)

Bug Fixes

• fix semver vulnerability (#​1071) (3f5c99d), closes #​1019

v7.0.1: conventional-changelog-conventionalcommits: v7.0.1

Compare Source

Bug Fixes

• conventional-changelog-conventionalcommits: include constants.js in package (#​1095) (a730b18), closes #​1093

v7.0.0: conventional-changelog-conventionalcommits: v7.0.0

Compare Source

⚠ BREAKING CHANGES

• Node >= 16 is required
• Now all presets are exports preset config factory function. conventional-changelog-preset-loader now exports new loadPreset and createPresetLoader functions. If you are using presets indirectly, using preset name, no any changes in configuration needed, just upgrade packages to latest versions.

Features

• conventional-changelog-conventionalcommits: add support for alphanumeric issues (#​1080) (f9b1897)
• drop node 14 support (#​1085) (1bce036)
• git-raw-commits: ignore commits by regex (#​1063) (47033e6)
• types: allow combining provided types with defaults (#​1064) (7ec8a18)
• unified presets interface (#​1045) (8d0ffbe)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[cbou]

@stevemao would be great to merge this PR :)

[stevemao]

Could you please take a look why ci fails?

[TimothyJones]

I'm not sure that merging this would achieve much - this package is deprecated (see here for discussion).

You could have a look at this fork that is maintained (by me) here. I'd like to update all the conventional-changelog dependencies, but I haven't had the time for a close read of the changelogs yet (the code is tightly coupled to the conventional-changelog dependencies, and some of their boundaries are exposed directly). Because the boundaries of the internal packages are exposed, I suspect that at least one breaking change is lurking in there somewhere. A PR where someone has figured out whether this is the case (and what the release notes should) be would be extremely welcome.

Anyway, CI fails because it runs on versions of node that the latest conventional-recommended-bump doesn't support.

[cbou]

Thanks @TimothyJones
That's exactly how you mentioned. The CI fails because of node versions.

I was actually looking for the possibility to pass multiple paths to git-raw-commits.
I solved it by using this:

  "dependencies": {
    "standard-version": "^9.5.0"
  },
  "overrides": {
    "standard-version": {
      "git-raw-commits": "4.0.0"
    }
  },

Maybe it can help someone else...

[TimothyJones]

Yep, that will work. I’d recommend switching to commit-and-tag-version (a drop in replacement) if you can- since it’s maintained and tested against current node versions.