Bump cf-java-client.version from 4.9.0.RELEASE to 4.12.0.RELEASE

[dependabot-preview[bot]]

Bumps cf-java-client.version from 4.9.0.RELEASE to 4.12.0.RELEASE. Updates cloudfoundry-client-reactor from 4.9.0.RELEASE to 4.12.0.RELEASE

Release notes

Sourced from cloudfoundry-client-reactor's releases.

Cloud Foundry Java Client 4.12.0.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 4.12.0.RELEASE. This release's theme is V3 functionality.

Note: This version now uses Spring Boot 2.3.x to manage most of its dependencies. This should have no impact on functionality.

• Added support for V3 Service Plans
• Complete support for V3 Applications
• Added support for V3 Admin
• Dependency updates.

For a more detailed look at the changes in 4.12.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 4.11.0.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 4.11.0.RELEASE. This release's theme is updates.

Note: This version now uses Spring Boot 2.3.x to manage most of its dependencies. This should have no impact on functionality.

• Added Java 11 unit tests to the existing Java 8 tests (via Guillaume Berche and in part thanks to him). Note that Java 8 is still our default target.
• Fixed Enabling of Public Visibility (via Arghya Sadhu, with thanks to Alexander Tsvetkov)
• Support for the latest version of the Cloud Foundry API (2.150.0)
• Dependency updates.

For a more detailed look at the changes in 4.11.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 4.10.0.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 4.10.0.RELEASE. This release's highlight is increased support for V3 endpoints at the client level.

Note: There is a known issue with the 4.1.51.Final version of Netty that breaks application upload for us. Our current dependencies avoid that version, but you may see a problem if you override our choice in your own dependencies.

• Better handling of opaque refresh tokens (via @sms0070)
• Fix the V3 application scaling request (with thanks to Encho Belezirev)
• Fix a potential error due to a reactor blocking call (with thanks to Ben Hale)
• Added support for the V3 Organizations and V3 Application Features endpoints.
• Documentation updates.

For a more detailed look at the changes in 4.10.0.RELEASE, please take a look at the issue tracker and commit log.

Commits

• 1149e0a v4.12.0.RELEASE Release
• 2098af2 Merge branch '3.x' into main
• 1b95cc7 v3.30.0.BUILD-SNAPSHOT Development
• ede39cc Merge branch '3.x' into main
• 444a2a6 Merge branch 'dep-updates' into 3.x
• 2536f68 Update Dependencies
• e850142 Merge branch '3.x' into main
• 0e80f06 Merge branch 'v3-admin' into 3.x
• a0db646 Add Admin V3 Support
• 461d8e0 Merge branch '3.x' into main
• Additional commits viewable in compare view

Updates cloudfoundry-operations from 4.9.0.RELEASE to 4.12.0.RELEASE

Release notes

Sourced from cloudfoundry-operations's releases.

Cloud Foundry Java Client 4.12.0.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 4.12.0.RELEASE. This release's theme is V3 functionality.

Note: This version now uses Spring Boot 2.3.x to manage most of its dependencies. This should have no impact on functionality.

• Added support for V3 Service Plans
• Complete support for V3 Applications
• Added support for V3 Admin
• Dependency updates.

For a more detailed look at the changes in 4.12.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 4.11.0.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 4.11.0.RELEASE. This release's theme is updates.

Note: This version now uses Spring Boot 2.3.x to manage most of its dependencies. This should have no impact on functionality.

• Added Java 11 unit tests to the existing Java 8 tests (via Guillaume Berche and in part thanks to him). Note that Java 8 is still our default target.
• Fixed Enabling of Public Visibility (via Arghya Sadhu, with thanks to Alexander Tsvetkov)
• Support for the latest version of the Cloud Foundry API (2.150.0)
• Dependency updates.

For a more detailed look at the changes in 4.11.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 4.10.0.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 4.10.0.RELEASE. This release's highlight is increased support for V3 endpoints at the client level.

Note: There is a known issue with the 4.1.51.Final version of Netty that breaks application upload for us. Our current dependencies avoid that version, but you may see a problem if you override our choice in your own dependencies.

• Better handling of opaque refresh tokens (via @sms0070)
• Fix the V3 application scaling request (with thanks to Encho Belezirev)
• Fix a potential error due to a reactor blocking call (with thanks to Ben Hale)
• Added support for the V3 Organizations and V3 Application Features endpoints.
• Documentation updates.

For a more detailed look at the changes in 4.10.0.RELEASE, please take a look at the issue tracker and commit log.

Commits

• 1149e0a v4.12.0.RELEASE Release
• 2098af2 Merge branch '3.x' into main
• 1b95cc7 v3.30.0.BUILD-SNAPSHOT Development
• ede39cc Merge branch '3.x' into main
• 444a2a6 Merge branch 'dep-updates' into 3.x
• 2536f68 Update Dependencies
• e850142 Merge branch '3.x' into main
• 0e80f06 Merge branch 'v3-admin' into 3.x
• a0db646 Add Admin V3 Support
• 461d8e0 Merge branch '3.x' into main
• Additional commits viewable 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

Superseded by #225.