chore(deps): update dependency python-semantic-release to v9.6.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
python-semantic-release (changelog)	==9.5.0 -> ==9.6.0

---

Release Notes

python-semantic-release/python-semantic-release (python-semantic-release)

v9.6.0

Compare Source

Feature

• feat: changelog filters are specialized per vcs type (#​890)

• test(github): sync pr url expectation with GitHub api documentation

• fix(github): correct changelog filter for pull request urls

• refactor(hvcs-base): change to an abstract class & simplify interface

• refactor(remote-hvcs-base): extend the base abstract class with common remote base class

• refactor(github): adapt to new abstract base class

• refactor(gitea): adapt to new abstract base class

• refactor(gitlab): adapt to new abstract base class

• refactor(bitbucket): adapt to new abstract base class

• refactor(cmds): prevent hvcs from executing if not remote hosted vcs

• feat(changelog): changelog filters are hvcs focused

• test(hvcs): add validation for issue_url generation

• feat(changelog-github): add issue url filter to changelog context

• feat(changelog-gitea): add issue url filter to changelog context

• refactor(cmd-version): consolidate asset uploads with release creation

• style: resolve ruff errors

• feat(changelog-context): add flag to jinja env for which hvcs is available

• test(changelog-context): demonstrate per hvcs filters upon render

• docs(changelog-context): explain new hvcs specific context filters

• refactor(config): adjust default token resolution w/ subclasses (76ed593)

Fix

• fix(parser-custom): gracefully handle custom parser import errors (67f6038)

• fix: correct version --prerelease use & enable --as-prerelease (#​647)

• test(version): add validation of --as-prerelease and --prerelease opts

• fix(version-cmd): correct --prerelease use

  Prior to this change, --prerelease performed the role of converting whichever forced
  version into a prerelease version declaration, which was an unintentional breaking
  change to the CLI compared to v7.

  --prerelease now forces the next version to increment the prerelease revision,
  which makes it consistent with --patch, --minor and --major. Temporarily disabled
  the ability to force a prerelease.

  Resolves: #​639

• feat(version-cmd): add --as-prerelease option to force the next version to be a prerelease

  Prior to this change, --prerelease performed the role that --as-prerelease now does,
  which was an unintentional breaking change to the CLI compared to v7.

  --prerelease is used to force the next version to increment the prerelease revision,
  which makes it consistent with --patch, --minor and --major, while --as-prerelease
  forces for the next version to be converted to a prerelease version type before it is
  applied to the project regardless of the bump level.

  Resolves: #​639

• docs(commands): update version command options definition about prereleases

---

Co-authored-by: codejedi365 <codejedi365@​gmail.com> (2acb5ac)

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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.