Skip to content


You can find the source of this version on GitHub at cloudfoundry/cf-release. It was created based on the commit 6247d0e4.

Release Notes

IMPORTANT - Known issue with the Create Account flow in UAA UI which causes infinite redirects. The workaround is to set login.links.homeRedirect: null in the cf-release manifest - Known issue with /check_token failing on GET request. - This release includes breaking changes for OAuth clients thats are defined in the cf-release manifest. Starting with UAA Release v36 we have added validation for OAuth Clients. You can find the full list here, but below are the changes deployers are most likely to see: - For cf client please ensure that secret is set to empty string '' - For ssh-proxy replace redirect-uri of /login with https://login.{system-domain}/login

Contents - Notices - Job Spec Changes - Security Notices - Compatible Releases and Stemcells - Subcomponent Updates


  • Starting with this release, CF deployments will use Diego as its default backend. This change comes in advance of the DEAs being officially deprecated on May 22.
  • The Postgres job will upgrade PostgreSQL to version 9.6.3. This drops support for upgrading from PostgreSQL 9.4.6. Only upgrades from PostgreSQL 9.4.9 (since cf v241) and PostgreSQL 9.6.2 (since cf v256) are supported. Before deploying, please review considerations at postgres-release v17.

Job Spec Changes

  • Not yet updated

Security Notices

Affecting v260

  • None

Resolved in v260

Subcomponent Updates

Compatible Releases and Stemcells


You can reference this release in your deployment manifest from the releases section:

- name: "cf"
  version: "260"
  url: ""
  sha1: "7d0f91ecbaef48f01ec7830d04e1bf5e45558deb"

Or upload it to your director with the upload-release command:

bosh upload-release --sha1 7d0f91ecbaef48f01ec7830d04e1bf5e45558deb \