chore(deps): bump github.com/hetznercloud/hcloud-go/v2 from 2.32.0 to 2.33.0#17762
Conversation
e2e0c90 to
cb0d3e4
Compare
|
Can we keep the label backwards compatible? |
Do you mean the |
|
I'd say: keep the same value for now, announce in CHANGELOG.md that we will remove the label in the next minor release due to upstream removing it. |
@roidelapluie Sounds sensible, will take care of it 👍 |
|
@roidelapluie I reverted the code change, and just disabled linting of the relevant lines. Does the release note look like what you had in mind? How do we make sure that the change is actually done in the next minor release? |
Bumps [github.com/hetznercloud/hcloud-go/v2](https://github.com/hetznercloud/hcloud-go) from 2.32.0 to 2.33.0. - [Release notes](https://github.com/hetznercloud/hcloud-go/releases) - [Changelog](https://github.com/hetznercloud/hcloud-go/blob/main/CHANGELOG.md) - [Commits](hetznercloud/hcloud-go@v2.32.0...v2.33.0) --- updated-dependencies: - dependency-name: github.com/hetznercloud/hcloud-go/v2 dependency-version: 2.33.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…ation The hcloud-go v2.33.0 deprecates server.Datacenter in favor of server.Location. This updates the hcloud discovery to use the new API. Note: __meta_hetzner_datacenter now contains the location name (e.g., "fsn1") instead of the datacenter name (e.g., "fsn1-dc8"), making it equivalent to __meta_hetzner_hcloud_datacenter_location. The label is kept for backwards compatibility with existing relabel configs. Signed-off-by: Arve Knudsen <[email protected]>
Signed-off-by: Arve Knudsen <[email protected]>
745c470 to
317fc81
Compare
roidelapluie
left a comment
There was a problem hiding this comment.
Yes, LGTM
I'd create an issue for the next release (you can assign to me).
|
I made an issue @roidelapluie. Thanks! |
Bumps github.com/hetznercloud/hcloud-go/v2 from 2.32.0 to 2.33.0.
NB:
server.Datacenteris deprecated in favor ofserver.Location. As a result,__meta_hetzner_datacenternow contains the location name (e.g., "fsn1") instead of the datacenter name (e.g., "fsn1-dc8"), making it equivalent to__meta_hetzner_hcloud_datacenter_location. The label is kept for backwards compatibility with existing relabel configs. @mmorel-35 I think you've been working on discovery/hetzner, do you think the change to__meta_hetzner_datacenteris OK?Release notes
Sourced from github.com/hetznercloud/hcloud-go/v2's releases.
Changelog
Sourced from github.com/hetznercloud/hcloud-go/v2's changelog.
Commits
6684746chore(main): release v2.33.0 (#779)f4ecfa7feat: default to max per page value inAllWithOpts(#794)0922bbafeat: deprecate datacenter inprimary ipsandservers(#793)6afa559deps: update actions/cache action to v5 (#789)5b818cechore: revert Storage Box support no longer experimental (#788)e4d7324ci: remove stale bot workflow (#787)cf0f52edeps: update pre-commit hook golangci/golangci-lint to v2.7.2 (#785)60400d7deps: update golang.org/x/ (#786)110bd4ddeps: update pre-commit hook golangci/golangci-lint to v2.7.1 (#784)daf9cf4feat: Storage Box support no longer experimental (#783)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)