[dependabot]

Bumps github.com/hetznercloud/hcloud-go/v2 from 2.50.0 to 2.52.0.

Release notes

Sourced from github.com/hetznercloud/hcloud-go/v2's releases.

v2.52.0

Load Balancers can now be created with existing Primary IPs

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 instead of having an IP address allocated automatically. Currently, you cannot change the Primary IP once the Load Balancer has been created.

To support this change, we added the new public_net property to the request body of the endpoint POST /load_balancers, with the following child properties:

• public_net.ipv4: ID of an IPv4 Primary IP to assign to the Load Balancer.
• public_net.ipv6: ID of an IPv6 Primary IP to assign to the Load Balancer.

If you omit a property, a new Primary IP of that version is allocated for the Load Balancer, as before.

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.

Related to https://docs.hetzner.cloud/changelog#2026-10-05-load-balancers-can-use-existing-primary-ips.

Deleting a Load Balancer now returns an Action

[!IMPORTANT] Please update all code that accesses LoadBalancerClient.Delete to use LoadBalancerClient.DeleteWithResult method instead.

As part of our work on supporting existing Primary IPs for Load Balancers, deleting a Load Balancer is now tracked with an Action.

The endpoint DELETE /load_balancers/{id} now returns a 201 status code with an Action in the response body, instead of a 204 status code with an empty response body.

You can use the returned Action to track the progress of the deletion.

Related to https://docs.hetzner.cloud/changelog#2026-10-05-delete-load-balancer-returns-action.

Features

• allow creating load balancers with primary ips (#932) (b092899)
• delete load balancer now returns an action (#932) (b092899)

v2.51.0

Features

• deprecate "token_readonly" error code (#930) (010d5c5)

Changelog

Sourced from github.com/hetznercloud/hcloud-go/v2's changelog.

v2.52.0

Compare to previous version

Load Balancers can now be created with existing Primary IPs

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 instead of having an IP address allocated automatically. Currently, you cannot change the Primary IP once the Load Balancer has been created.

To support this change, we added the new public_net property to the request body of the endpoint POST /load_balancers, with the following child properties:

• public_net.ipv4: ID of an IPv4 Primary IP to assign to the Load Balancer.
• public_net.ipv6: ID of an IPv6 Primary IP to assign to the Load Balancer.

If you omit a property, a new Primary IP of that version is allocated for the Load Balancer, as before.

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.

Related to https://docs.hetzner.cloud/changelog#2026-10-05-load-balancers-can-use-existing-primary-ips.

Deleting a Load Balancer now returns an Action

[!IMPORTANT] Please update all code that accesses LoadBalancerClient.Delete to use LoadBalancerClient.DeleteWithResult method instead.

As part of our work on supporting existing Primary IPs for Load Balancers, deleting a Load Balancer is now tracked with an Action.

The endpoint DELETE /load_balancers/{id} now returns a 201 status code with an Action in the response body, instead of a 204 status code with an empty response body.

You can use the returned Action to track the progress of the deletion.

Related to https://docs.hetzner.cloud/changelog#2026-10-05-delete-load-balancer-returns-action.

Features

• allow creating load balancers with primary ips (#932) (b092899)
• delete load balancer now returns an action (#932) (b092899)

v2.51.0

Compare to previous version

Features

• deprecate "token_readonly" error code (#930) (010d5c5)

Commits

• cea7071 chore(main): release v2.52.0 (#933)
• b092899 feat: allow creating load balancers with primary ips (#932)
• 21b0e65 chore(main): release v2.51.0 (#931)
• 010d5c5 feat: deprecate "token_readonly" error code (#930)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)