chore(deps): bump python-semantic-release/python-semantic-release from 9.1.1 to 9.8.7

[dependabot[bot]]

Bumps python-semantic-release/python-semantic-release from 9.1.1 to 9.8.7.

Release notes

Sourced from python-semantic-release/python-semantic-release's releases.

v9.8.7 (2024-08-20)

Fixes

• Provide context.history global in release notes templates (#1005, 5bd91b4)

• release-notes: provide context.history global in release note templates (5bd91b4)

• release-notes: fix noop-changelog to print raw release notes (5bd91b4)

Documentation

• Use pinned version for GHA examples (#1004, 5fdf761)

• changelog: clarify description of the default changelog generation process (399fa65)

• configuration: clarify changelog_file vs template_dir option usage (a7199c8)

• configuration: fix build_command_env table rendering (#996, a5eff0b)

• github-actions: adjust formatting & version warning in code snippets (5fdf761)

• github-actions: use pinned version for GHA examples (5fdf761)

Issues Resolved

• #983: When template folder is present, changelog_file is ignored

• #984: jinja2.exceptions.UndefinedError: 'context' is undefined

• #1003: pinning GHA workflow

---

Detailed Changes: https://github.com/python-semantic-release/python-semantic-release/compare/v9.8.6...v9.8.7

v9.8.6 (2024-07-20)

Fixes

• version-cmd: resolve build command execution in powershell (#980, 32c8e70)

Documentation

• configuration: correct GHA parameter name for commit email (#981)

---

Detailed Changes: https://github.com/python-semantic-release/python-semantic-release/compare/v9.8.5...v9.8.6

... (truncated)

Changelog

Sourced from python-semantic-release/python-semantic-release's changelog.

v9.8.7 (2024-08-20)

Documentation

• docs: use pinned version for GHA examples (#1004)

• docs(github-actions): use pinned version for GHA examples

  Fixes #1003

• chore(scripts): add auto version bump to non dynamic docs text (i.e. code snippets)

• docs(github-actions): adjust formatting & version warning in code snippets

• style(docs-github-actions): adjust formatting for readability

---

Co-authored-by: codejedi365 <codejedi365@gmail.com> (5fdf761)

• docs(configuration): fix build_command_env table rendering (#996) (a5eff0b)

• docs(changelog): clarify description of the default changelog generation process (399fa65)

• docs(configuration): clarify changelog_file vs template_dir option usage

Provided additional description that warns about the mutually-exclusive nature of the changelog_file option and the template_dir option.

Resolves: #983 (a7199c8)

Fix

• fix: provide context.history global in release notes templates (#1005)

• fix(release-notes): provide context.history global in release note templates

  Temporarily return the context.history variable to release notes generation as many users are using it in their release documentation. It was never intended to be provided and will be removed in the future.

  context was removed in v9.8.3 during a refactor and condensing of changelog and release notes functionality.

  Resolves: #984

• fix(release-notes): fix noop-changelog to print raw release notes

  Some markdown sequences can be interpreted as ansi escape sequences which dilute debugging of release note templates by the user. This change ensures the raw

... (truncated)

Commits

• 708671d 9.8.7
• 5bd91b4 fix: provide context.history global in release notes templates (#1005)
• f45d60d style: beautify 5fdf7614c036a77ffb051cd30f57d0a63c062c0d
• 5fdf761 docs: use pinned version for GHA examples (#1004)
• a5eff0b docs(configuration): fix build_command_env table rendering (#996)
• 4e59b50 build(deps-dev): update pytest requirement from ~=7.0 to ~=8.3 (#987)
• 399fa65 docs(changelog): clarify description of the default changelog generation process
• a7199c8 docs(configuration): clarify changelog_file vs template_dir option usage
• de86b09 chore(github): improve issue reporting template formats & input
• 95fc664 chore(github): add pull request template
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #669.