build(deps): downgrade @release-it/conventional-changelog to 10.0.1

[lampajr]

Thank you for submitting this pull request

Prepare release is currently failing with:

Run next_version=$(npx release-it --release-version --no-git.requireCleanWorkingDir)
  next_version=$(npx release-it --release-version --no-git.requireCleanWorkingDir)
  echo "NEXT_VERSION=${next_version}" >> $GITHUB_ENV
  shell: /usr/bin/bash -e {0}
  env:
    GITHUB_TOKEN: ***
    NPM_TOKEN: ***
ERROR whatBump is not a function
Error: Process completed with exit code 1.

See job https://github.com/kiegroup/git-backporting/actions/runs/19697906640/job/56427566209

Description

This error seems related to some issue in @release-it/conventional-changelog, and as reported here the suggestion was to downgrade it. Therefore, let's try to downgrade the package to the latest version used in v4.8.6 where it was working.

How Has This Been Tested?

Checklist

• Tests added if applicable.
• Documentation updated if applicable.

Merge criteria:

• The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

Note: dist/cli/index.js and dist/gha/index.js are automatically generated by git hooks and gh workflows.

First time here?

This project follows git conventional commits pattern, therefore the commits should have the following format:

<type>(<optional scope>): <subject>
empty separator line
<optional body>
empty separator line
<optional footer>

Where the type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test]

NOTE: if you are still in a work in progress branch and you want to push your changes remotely, consider adding --no-verify for both commit and push, e.g., git push origin <feat-branch> --no-verify - this could become useful to push changes where there are still tests failures. Once the pull request is ready, please amend the commit and force-push it to keep following the adopted git commit standard.

How to prepare for a new release?

There is no need to manually update package.json version and CHANGELOG.md information. This process has been automated in Prepare Release Github workflow.

Therefore whenever enough changes are merged into the main branch, one of the maintainers will trigger this workflow that will automatically update version and changelog based on the commits on the git tree.

More details can be found in package release section of the README.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	89.2%	504/565
🟢	Branches	85.46%	241/282
🟢	Functions	87.5%	112/128
🟢	Lines	89.05%	488/548

Test suite run success

217 tests passing in 18 suites.

Report generated by 🧪jest coverage report action from 4f802ed