Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update module github.com/cloudscale-ch/cloudscale-go-sdk to v4 - autoclosed #72

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 9, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/cloudscale-ch/cloudscale-go-sdk v1.11.0 -> v4.0.0 age adoption passing confidence

Release Notes

cloudscale-ch/cloudscale-go-sdk (github.com/cloudscale-ch/cloudscale-go-sdk)

v4.0.0: cloudscale-go-sdk v4.0.0

Compare Source

What's new:

  • At LoadBalancer property to all descendant resources of LoadBalancer, not only direct children:
    • Add LoadBalancerPoolMember.LoadBalancer
    • Add LoadBalancerHealthMonitor.LoadBalancer
    • Add LoadBalancerListener.LoadBalancer
  • Bump golang.org/x/net from 0.7.0 to 0.17.0..

Breaking Change:

  • LoadBalancerListener.Pool is now *LoadBalancerPoolStub instead of LoadBalancerPoolStub.
    Ensure your code has nil checks before accessing fields of LoadBalancerListener.Pool.
    When using the "tcp" protocol, a pool will always be set. However, in the future
    listeners for other protocols might not have a pool assigned. Note: the Load Balancer API is still in beta as of this
    writing.

Full Changelog: cloudscale-ch/cloudscale-go-sdk@v3.0.0...v4.0.0

v3.0.0: cloudscale-go-sdk v3.0.0

Compare Source

What's new:

  • Add support for cloudscale.ch Load Balancers.
  • Add FloatingIP to LoadBalancer and related types.
  • Switch to go 1.18.
  • Add INTEGRATION_TEST_ZONE for injecting test zone.
  • Bump golang.org/x/net from 0.0.0-20190108225652-1e06a53dbb7e to 0.7.0.

Breaking Change:

  • ServerRequest.Volumes is now *[]ServerVolumeRequest instead of *[]Volume. You will see compile errors after upgrading which should be easily resolvable by replacing Volume with ServerVolumeRequest.

Full Changelog: cloudscale-ch/cloudscale-go-sdk@v2.1.0...v3.0.0

v2.1.0: cloudscale-go-sdk v2.1.0

Compare Source

What's new:

  • Add FirmwareType property to CustomImage and CustomImageImport.

Full Changelog: cloudscale-ch/cloudscale-go-sdk@v2.0.1...v2.1.0

v2.0.1: cloudscale-go-sdk v2.0.1

Compare Source

What's new:

  • The v2.0.0 release was broken, this release should fix the problems.

Full Changelog: cloudscale-ch/cloudscale-go-sdk@v2.0.0...v2.0.1

v2.0.0: cloudscale-go-sdk v2.0.0

Compare Source

Breaking:

  • Tags are now references. This makes it possible to pass an empty {}. Previously this was made impossible, because of omitempty. If you are not using tags, everything should still working like in 1.x.x.

Full Changelog: cloudscale-ch/cloudscale-go-sdk@v1.11.0...v2.0.0


Configuration

📅 Schedule: 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependency label Jan 9, 2024
@simu simu mentioned this pull request Feb 13, 2024
3 tasks
@renovate renovate bot changed the title Update module github.com/cloudscale-ch/cloudscale-go-sdk to v4 Update module github.com/cloudscale-ch/cloudscale-go-sdk to v4 - autoclosed Feb 13, 2024
@renovate renovate bot closed this Feb 13, 2024
@renovate renovate bot deleted the renovate/github.com-cloudscale-ch-cloudscale-go-sdk-4.x branch February 13, 2024 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants