Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 6, 2025

This PR contains the following updates:

Package Change Age Confidence
semantic-release-pypi 5.1.1 -> 5.1.3 age confidence

Release Notes

abichinger/semantic-release-pypi (semantic-release-pypi)

v5.1.3

Compare Source

Bug Fixes
  • skip setup.py version check when versionCmd is set (1edc393)
  • support array for versionCmd and improve process handling (b7cf82b)

v5.1.2

Compare Source

Bug Fixes
  • remove --skip-existing flag due to unsupported in twine 6.2.0 (#​46) (89e782d)

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/semantic-release-pypi-5.x-lockfile branch from b432ae3 to 76b43d8 Compare September 25, 2025 20:14
@renovate renovate bot force-pushed the renovate/semantic-release-pypi-5.x-lockfile branch from 76b43d8 to b26d8c6 Compare September 28, 2025 20:30
@renovate renovate bot changed the title chore(deps): update dependency semantic-release-pypi to v5.1.2 chore(deps): update dependency semantic-release-pypi to v5.1.3 Sep 28, 2025
@sonarqubecloud
Copy link

@mivek mivek merged commit 4f46a7a into main Nov 25, 2025
12 checks passed
@mivek mivek deleted the renovate/semantic-release-pypi-5.x-lockfile branch November 25, 2025 06:41
@github-actions
Copy link

🎉 This PR is included in version 1.10.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants