Java buildpack major version upgrade, v5, default version
Earlier this year the Cloud Foundry Java buildpack team completed a major rewrite, version 5, of the Java buildpack which removed legacy code and introduced breaking changes related to how Java apps are built and deployed. In May 2026, we provided an update in a news article which discussed the Cloud.gov Java buildpack being upgraded and what customers needed to prepare for this change. November 12, 2026, we will be updating the platform buildpacks so that version 5 of the Java buildpack is the default version. If you have not already performed testing and made the necessary changes so that your application is compatible with using version 5 of the Java buildpack please consider pinning your buildpack version to an older version.
How to pin your buildpack version
Option A will override anything you specify in your manifest, however the buildpack specified in your manifest.yml file is what will be referenced if you restage your application. Note that pinning to older versions means you won't receive the latest security updates and features. Please upgrade as soon as possible.
Option A: Pin your buildpack version using the cf push command
Run the following command to deploy your app with the an older buildpack version:
cf push MY_APP --buildpack https://github.com/cloudfoundry/java-buildpack#v4.77.0.git
Option B: Pin your buildpack version using your manifest.yml file
Add the older Java buildpack specification to your manifest file:
...
buildpacks:
- https://github.com/cloudfoundry/java-buildpack#v4.77.0.git
...
Then deploy normally with cf push.
Pro tip: Test in a non-production environment first to validate behavior without undue risk.
Questions? Contact Cloud.gov support for assistance.