I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.5.0.RELEASE. This release has more CI changes, but does not change the library. Upgrading is optional.
For a more detailed look at the changes in 5.5.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 5.4.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.4.0.RELEASE. This release is for CI & incorporates changes in how CI is being done.
For a more detailed look at the changes in 5.4.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 5.3.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.3.0.RELEASE. This release is the same as 5.2.0.
For a more detailed look at the changes in 5.1.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 5.2.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.2.0.RELEASE. This release improves compatibility with CAPI.
Make state field nullable (with thanks to @alek-sys)
For a more detailed look at the changes in 5.2.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 5.1.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.1.0.RELEASE. This release's theme is V3 functionality.
Added support for V3 Roles (with thanks to Rangel Ivanov)
Added support for renaming spaces (with thanks to Mike Heath)
Dependency updates.
For a more detailed look at the changes in 5.1.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 5.0.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.0.0.RELEASE. This release's theme is V3 functionality.
Note: This is the first version in the 5.x line. Many of its dependencies are now managed by Spring Boot 2.4, which means a non-trivial update in the underlying versions of Project Reactor dependencies we rely on. This may mean some refactoring is required from you. In addition the V3 Service Instances package has been renamed, which will require a straightforward refactor if you use that.
Added support for Automatic Module Names (with thanks to Alexander Tsvetkov)
Added support for Log Cache Client (with thanks to Mike Heath)
Added support for V3 Buildpacks
Added support for V3 Service Offerings
Rename the serviceInstances package to serviceinstances for consistency.
Dependency updates.
For a more detailed look at the changes in 5.0.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 4.15.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 4.15.0.RELEASE. This release's theme is CI improvements.
Several changes were made as part of CI updates
Make state field nullable (with thanks to @alek-sys)
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.5.0.RELEASE. This release has more CI changes, but does not change the library. Upgrading is optional.
For a more detailed look at the changes in 5.5.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 5.4.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.4.0.RELEASE. This release is for CI & incorporates changes in how CI is being done.
For a more detailed look at the changes in 5.4.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 5.3.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.3.0.RELEASE. This release is the same as 5.2.0.
For a more detailed look at the changes in 5.1.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 5.2.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.2.0.RELEASE. This release improves compatibility with CAPI.
Make state field nullable (with thanks to @alek-sys)
For a more detailed look at the changes in 5.2.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 5.1.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.1.0.RELEASE. This release's theme is V3 functionality.
Added support for V3 Roles (with thanks to Rangel Ivanov)
Added support for renaming spaces (with thanks to Mike Heath)
Dependency updates.
For a more detailed look at the changes in 5.1.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 5.0.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 5.0.0.RELEASE. This release's theme is V3 functionality.
Note: This is the first version in the 5.x line. Many of its dependencies are now managed by Spring Boot 2.4, which means a non-trivial update in the underlying versions of Project Reactor dependencies we rely on. This may mean some refactoring is required from you. In addition the V3 Service Instances package has been renamed, which will require a straightforward refactor if you use that.
Added support for Automatic Module Names (with thanks to Alexander Tsvetkov)
Added support for Log Cache Client (with thanks to Mike Heath)
Added support for V3 Buildpacks
Added support for V3 Service Offerings
Rename the serviceInstances package to serviceinstances for consistency.
Dependency updates.
For a more detailed look at the changes in 5.0.0.RELEASE, please take a look at the issue tracker and commit log.
Cloud Foundry Java Client 4.15.0.RELEASE
I'm pleased to announce the release of the Cloud Foundry Java Client, version 4.15.0.RELEASE. This release's theme is CI improvements.
Several changes were made as part of CI updates
Make state field nullable (with thanks to @alek-sys)
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)
Bumps
cf-java-client.version
from 4.9.0.RELEASE to 5.5.0.RELEASE. Updatescloudfoundry-client-reactor
from 4.9.0.RELEASE to 5.5.0.RELEASERelease notes
Sourced from cloudfoundry-client-reactor's releases.
... (truncated)
Commits
0bf8b7c
v5.5.0.RELEASE Release7256ba3
Remove storing the build info, no longer needed. This is pulled by the artifa...2431f9e
- Remove CI information from README as it's no longer publice4eea16
Updates dockerfile & maven promotion scriptsd1adae8
Updates to CI for promote to maven020725c
Change JAR name in imagedee4bdf
Bump snapshot versions to 5.4.081ea151
Removing Bintray & using https://github.com/spring-io/concourse-release-scrip...cfddc2d
Add the concourse release script JAR into the imagef37dad6
Fixes issue with failing integration tests. This test was changing the availa...Updates
cloudfoundry-operations
from 4.9.0.RELEASE to 5.5.0.RELEASERelease notes
Sourced from cloudfoundry-operations's releases.
... (truncated)
Commits
0bf8b7c
v5.5.0.RELEASE Release7256ba3
Remove storing the build info, no longer needed. This is pulled by the artifa...2431f9e
- Remove CI information from README as it's no longer publice4eea16
Updates dockerfile & maven promotion scriptsd1adae8
Updates to CI for promote to maven020725c
Change JAR name in imagedee4bdf
Bump snapshot versions to 5.4.081ea151
Removing Bintray & using https://github.com/spring-io/concourse-release-scrip...cfddc2d
Add the concourse release script JAR into the imagef37dad6
Fixes issue with failing integration tests. This test was changing the availa...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)