[](https://renovatebot.com)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [actions/setup-python](https://togithub.com/actions/setup-python) |
action | major | `v4` -> `v5` |
---
### Release Notes
<details>
<summary>actions/setup-python (actions/setup-python)</summary>
### [`v5`](https://togithub.com/actions/setup-python/compare/v4...v5)
[Compare
Source](https://togithub.com/actions/setup-python/compare/v4...v5)
</details>
---
### 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.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/ansible-collections/hetzner.hcloud).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy44Ny4yIiwidXBkYXRlZEluVmVyIjoiMzcuODcuMiIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
##### SUMMARY
pre-commit.ci automatically pushes styling commit to the release please
branch and might render the checkout in CI out of sync with the origin.
This makes sure the release-please workflow does not fail by force
pushing to the branch.
##### SUMMARY
Disable azure pipelines for draft pull requests and ask release-please
to create draft pull requests. This should reduce the amount of CI usage
around the release please workflow.
##### SUMMARY
The version tag regex allowing to publish to ansible-galaxy does not
allow versions to be prefixed with a v:
468493fef4/zuul.d/pipelines.yaml (L146-L155)
Introducing the v prefix is also breaking with the previous tag naming
convention.
##### SUMMARY
The current release process for this project requires multiple manual
local steps to prepare and then tag the release. This introduces the
standard release-please workflow we have in most of our integrations.
Release-please will open a new PR whenever there is a releasable change
and it updates the CHANGELOG & other files automatically in this PR.
Once the PR is merged a new tag is created.
This repository has some additional complexity as it uses
`antsibull-changelog` to maintain the user-facing changelog. This is
implemented ina second job in the `release-please` workflow which
executes when the release-please PR is updated and then runs
`antsibull-changelog release` against the version. The resulting changes
are pushed as a second commit to the same PR.
