Skip to content

Commit e109a64

Browse files
author
Hetzner Cloud Bot
committed
chore(main): release v2.27.0
1 parent 84e3a19 commit e109a64

3 files changed

Lines changed: 39 additions & 2 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,42 @@
11
# Changelog
22

3+
## [v2.27.0](https://github.com/hetznercloud/hcloud-python/releases/tag/v2.27.0)
4+
5+
[Compare to previous version](https://github.com/hetznercloud/hcloud-python/compare/v2.26.0...v2.27.0)
6+
7+
### Load Balancers can now be created with existing Primary IPs
8+
9+
Primary IPs, which were previously available exclusively for Servers, are now also available for Load Balancers. When creating a Load Balancer, you can assign an [existing Primary IP](https://docs.hetzner.cloud/reference/cloud#tag/primary-ips/list_primary_ips) instead of having an IP address allocated automatically. Currently, you cannot change the Primary IP once the Load Balancer has been created.
10+
11+
To support this change, we added the new `public_net` property to the request body of the endpoint [POST /load_balancers](https://docs.hetzner.cloud/reference/cloud#tag/load-balancers/create_load_balancer), with the following child properties:
12+
13+
- `public_net.ipv4`: ID of an IPv4 Primary IP to assign to the Load Balancer.
14+
- `public_net.ipv6`: ID of an IPv6 Primary IP to assign to the Load Balancer.
15+
16+
If you omit a property, a new Primary IP of that version is allocated for the Load Balancer, as before.
17+
18+
A Primary IP can currently only be assigned when the Load Balancer is created. It stays assigned for the entire lifetime of the Load Balancer.
19+
20+
Related to https://docs.hetzner.cloud/changelog#2026-10-05-load-balancers-can-use-existing-primary-ips.
21+
22+
### Deleting a Load Balancer now returns an Action
23+
24+
> [!IMPORTANT]
25+
> Please update all code that uses the `LoadBalancersClient.delete` method to wait on the newly returned action.
26+
27+
As part of our work on supporting [existing Primary IPs for Load Balancers](https://docs.hetzner.cloud/changelog#2026-10-05-load-balancers-can-use-existing-primary-ips), deleting a Load Balancer is now tracked with an Action.
28+
29+
The endpoint [DELETE /load_balancers/{id}](https://docs.hetzner.cloud/reference/cloud#tag/load-balancers/delete_load_balancer) now returns a 201 status code with an Action in the response body, instead of a 204 status code with an empty response body.
30+
31+
You can use the returned Action to track the progress of the deletion.
32+
33+
Related to https://docs.hetzner.cloud/changelog#2026-10-05-delete-load-balancer-returns-action.
34+
35+
### Features
36+
37+
- allow creating load balancers with primary ips (#700) ([84e3a19](https://github.com/hetznercloud/hcloud-python/commit/84e3a196ff29b2fc7508bce009b7d9da38005e49))
38+
- delete load balancer now returns an action (#700) ([84e3a19](https://github.com/hetznercloud/hcloud-python/commit/84e3a196ff29b2fc7508bce009b7d9da38005e49))
39+
340
## [v2.26.0](https://github.com/hetznercloud/hcloud-python/releases/tag/v2.26.0)
441

542
[Compare to previous version](https://github.com/hetznercloud/hcloud-python/compare/v2.25.1...v2.26.0)

‎hcloud/_version.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
from __future__ import annotations
22

3-
__version__ = "2.26.0" # x-releaser-pleaser-version
3+
__version__ = "2.27.0" # x-releaser-pleaser-version

‎setup.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77

88
setup(
99
name="hcloud",
10-
version="2.26.0", # x-releaser-pleaser-version
10+
version="2.27.0", # x-releaser-pleaser-version
1111
keywords="hcloud hetzner cloud",
1212
description="Official Hetzner Cloud python library",
1313
long_description=readme,

0 commit comments

Comments
 (0)