Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency python-semantic-release to v9.17.0 - autoclosed #796

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 12, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
python-semantic-release (changelog) 9.15.2 -> 9.17.0 age adoption passing confidence

Release Notes

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

v9.17.0

Compare Source

Bug Fixes
  • github-action: Disable writing python bytecode in action execution
    (#​1152,
    315ae21)

File permission issues can occur when using the github-action and dynamically loading files from the
repository. When importing, python generally will create bytecode files and write to disk as the
current user. Because the default user in the github action is root, those files are written as
root which means when it returns to the rest of the workflow, those files cannot be modified or
deleted. With this change, we disable writing of bytecode files which prevents any failures that
may result after the python-semantic-release action is executed.

Features
  • changelog: Add sort_numerically filter function to template environment
    (#​1146,
    7792388)
  • test(helpers): add unit tests for various prefixed number lists

  • test(changelog-context): add unit tests to validate use of sort_numerically filter

  • test(release-notes-context): add unit tests to validate use of sort_numerically filter

  • refactor(util): relocate sort_numerically function to top level

  • docs(changelog-templates): add description for new sort_numerically filter function

  • config: Extend support of remote urls aliased using git insteadOf configurations
    (#​1151,
    4045037)

Resolves: #​1150

  • refactor(hvcs): add validation of git urls upon vcs client initialization

  • test(hvcs): refactor unit test to catch validation error immediately of bad git url

  • test(config): add test case of a git insteadOf aliased origin

  • test(parser-angular): update unit tests for parser return value compatibility

  • test(parser-scipy): update unit tests for parser return value compatibility

  • test(parser-emoji): update unit tests for parser return value compatibility

  • feat(version): parse squashed commits individually

adds the functionality to separately parse each commit message within a squashed merge commit to
detect combined commit types that could change the version bump

  • feat(changelog): parse squashed commits individually

adds functionality to separately parse each commit message within a squashed merge commit which
decouples the commits into their respective type categories in the changelog.

  • refactor(helpers): centralize utility for applying multiple text substitutions

  • feat(parser-angular): upgrade angular parser to parse squashed commits individually

Resolves: #​1085

  • feat(parser-angular): apply PR/MR numbers to all parsed commits from a squash merge

  • feat(parser-emoji): add functionality to interpret scopes from gitmoji commit messages

  • feat(parser-emoji): upgrade emoji parser to parse squashed commits individually

  • test(fixtures): adjust parser for squashed commit definitions

  • test(fixtures): change config of github flow repo to parse squash commits

  • test(fixtures): add fixture to create gitlab formatted merge commit

  • refactor(parser-scipy): standardize all category spelling applied to commits

  • docs(commit-parsing): add description for squash commit evaluation option of default parsers

  • docs(configuration): update the commit_parser_options setting description

Performance Improvements
  • refactor: adjust logging output

v9.16.1

Compare Source

Bug Fixes
  • parser-custom: Handle relative parent directory paths to module file better
    (#​1142,
    c4056fc)

The dynamic import originally would just replace "/" with "." to make the import module name more
pythonic, however this would be problematic in monorepos which would use
"../../misc/commit_parser.py" to locate the parser and so the resulting sys.modules entry would
have numerous periods (.) as a prefix. This removes that possibility. Still always an issue if the
imported module name matches an existing module but the likelihood is low.

Documentation
  • github-actions: Update PSR versions in github workflow examples
    (#​1140,
    9bdd626)

v9.16.0

Compare Source

Bug Fixes
  • changelog: Fixes PSR release commit exclusions for customized commit messages
    (#​1139,
    f9a2078)
  • fix(config-changelog): validate changelog.exclude_commit_patterns on config load

  • test(fixtures): relocate sanitize changelog functions

  • test(cmd-version): add test to validate that custom release messages are ignored in changelog

  • test(config): add changelog.exclude_commit_patterns validation check

  • style(config): refactor import names of re module

  • cmd-version: Fix --print-tag result to match configured tag format
    (#​1134,
    a990aa7)
  • test(fixtures): add new trunk repo that has a different tag format

  • test(fixtures): add helper to extract config settings from repo action definition

  • test(cmd-version): expand testing of --print-tag & --print-last-released-tag

PSR did not have enough testing to demonstrate testing of the tag generation when the tag format was
configured differently than normal. This commit adds a significant portion of testing to exercise
the print tag functionality which must match the configured tag format.

  • cmd-version: Fix tag format on default version when force bump for initial release
    (#​1138,
    007fd00)

Resolves: #​1137

  • test(fixtures): add new unreleased trunk repo with a different tag format

  • test(cmd-version): ensure forced bump version on initial release follows tag format

ref: #​1137

Features
  • config: Expand dynamic parser import to handle a filepath to module
    (#​1135,
    0418fd8)
  • test(fixtures): remove import checking/loading of custom parser in use_custom_parser

  • test(config): extend import parser unit tests to evaluate file paths to modules

  • docs(commit-parsing): add the new custom parser import spec description for direct path imports

Resolves: #​687

  • docs(configuration): adjust commit_parser option definition for direct path imports

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 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/python-semantic-release-9.x-lockfile branch from a3e2ca7 to 5bcee77 Compare January 12, 2025 21:24
@renovate renovate bot changed the title chore(deps): update dependency python-semantic-release to v9.16.0 chore(deps): update dependency python-semantic-release to v9.16.1 Jan 12, 2025
@renovate renovate bot changed the title chore(deps): update dependency python-semantic-release to v9.16.1 chore(deps): update dependency python-semantic-release to v9.17.0 Jan 26, 2025
@renovate renovate bot force-pushed the renovate/python-semantic-release-9.x-lockfile branch from 5bcee77 to 6297b29 Compare January 26, 2025 04:43
@renovate renovate bot changed the title chore(deps): update dependency python-semantic-release to v9.17.0 chore(deps): update dependency python-semantic-release to v9.17.0 - autoclosed Jan 27, 2025
@renovate renovate bot closed this Jan 27, 2025
@renovate renovate bot deleted the renovate/python-semantic-release-9.x-lockfile branch January 27, 2025 00:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants