Commit graph

4 commits

Author SHA1 Message Date
Hetzner Cloud Bot
0c776c3fc8
chore(main): release 2.2.0 (#360)
🤖 I have created a release *beep* *boop*
---


##
[2.2.0](https://github.com/ansible-collections/hetzner.hcloud/compare/2.1.2...2.2.0)
(2023-10-23)


### Features

* add deprecation field to hcloud_iso_info
([#357](https://github.com/ansible-collections/hetzner.hcloud/issues/357))
([76ef636](76ef636f07))
* add load_balancer algorithm option
([#368](https://github.com/ansible-collections/hetzner.hcloud/issues/368))
([a93dbaa](a93dbaa428))
* allow selecting a resource using its ID
([#361](https://github.com/ansible-collections/hetzner.hcloud/issues/361))
([5e425c5](5e425c56c2))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
2023-10-23 16:26:55 +02:00
Jonas L
7f4e4e96cc
build: don't include v prefix in version tags (#349)
##### 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.
2023-10-06 15:59:20 +02:00
Hetzner Cloud Bot
e692b3e2e0
chore(main): release 2.1.2 (#335)
🤖 I have created a release *beep* *boop*
---


##
[2.1.2](https://github.com/ansible-collections/hetzner.hcloud/compare/2.1.1...v2.1.2)
(2023-10-05)


### Bug Fixes

* firewall port argument is required with udp or tcp
([#345](https://github.com/ansible-collections/hetzner.hcloud/issues/345))
([76c1abf](76c1abf447))
* invalid field in load_balancer_service health_check.http return data
([#333](https://github.com/ansible-collections/hetzner.hcloud/issues/333))
([fb35516](fb35516e76))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
2023-10-05 16:40:02 +02:00
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