ansible-collection-hetzner-.../changelogs/dev-changelog.md
Julian Tölle eb4114bad3
ci: setup release-please (#317)
##### 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.
2023-09-05 14:49:05 +02:00

8 lines
371 B
Markdown

# Dev Changelog
> [!WARNING]
> For the user changelog, please check out [CHANGELOG.rst](../CHANGELOG.rst) instead.
This file contains a list of changes intended towards developers. It is auto-generated by release-please.
We would prefer to not generate this file, but disabling this is not supported currently: https://github.com/googleapis/release-please/issues/2007