Skip to content

deps: update module github.com/hetznercloud/hcloud-go/v2 to v2.52.0 - autoclosed - #1499

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-hetznercloud-hcloud-go-v2-2.x
Closed

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-hetznercloud-hcloud-go-v2-2.x

Conversation

@renovate

@renovate renovate Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
github.com/hetznercloud/hcloud-go/v2 v2.50.0 → v2.52.0 age confidence

Release Notes

hetznercloud/hcloud-go (github.com/hetznercloud/hcloud-go/v2)

v2.52.0

Compare Source

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

v2.51.0

Compare Source

Compare to previous version

Features

Configuration

📅 Schedule: (UTC)

  • 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner October 5, 2026 09:23
@renovate renovate Bot changed the title deps: update module github.com/hetznercloud/hcloud-go/v2 to v2.51.0 deps: update module github.com/hetznercloud/hcloud-go/v2 to v2.52.0 Oct 5, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-hetznercloud-hcloud-go-v2-2.x branch from 4d5d84c to 69b2d81 Compare October 5, 2026 12:55
@renovate renovate Bot changed the title deps: update module github.com/hetznercloud/hcloud-go/v2 to v2.52.0 deps: update module github.com/hetznercloud/hcloud-go/v2 to v2.52.0 - autoclosed Oct 5, 2026
@renovate renovate Bot closed this Oct 5, 2026
@renovate
renovate Bot deleted the renovate/github.com-hetznercloud-hcloud-go-v2-2.x branch October 5, 2026 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants