Skip to content


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

Release Notes

The cf-release v195 was released on December 29th, 2014.


  • Upgrading Java Buildpack to v2.6 details
  • Upgrading nodejs buildpack to v1.1.1 details
  • Upgrading go buildpack to v1.1.1 details
  • Upgrading python buildpack to v1.1.1 details
  • Upgrading ruby buildpack to v1.2.0 details
  • Updated git inside warden container to 2.2.1 details
  • Add possibility to specify postgres role permissions in manifest details
  • Allow core files to be generated in warden details
  • Add in the ability to configure IP restrictions for the UAA and Login Server HTTP ports. details
  • Make the logging level of the collector configurable details
  • Randomize nats server selection details
  • make ha_proxy respect disabling timeout details
  • Fixed an issue where the DEA needed twice the space requested to successfully place an app details
  • More flexible nested domain creation rules details
  • DEA sends nats heartbeat even when there are no running instances This keeps HM9000 from thinking there are problems. details
  • Retry polling on the state of the upload if error is an HTTP timeout details
  • Sets the status code for upgrade to Websocket and TCP scenarios details
  • Bump apcera/nats to v1.0.6 details
  • Fixed issue where router does not start if dropsonde is misconfigured details
  • Prune routes when no connection to NATS is established details
  • Fixed an issue with leaking file descriptors details
  • Fix key type issue in graphite historian details
  • Enhanced Graphite and router metrics details
  • Fixed Mysql 5.6 issue on timestamp creation details
  • Fixed issue where deadlocks were happening on delayed job workers details
  • Work continues on Application Process Types details
  • Update Service Plan completed details
  • Work continues on Service Audit Events details
  • Removed unnecessary warning when plans without instances are deleted during broker catalog sync details
  • Fixed SpaceDeveloper able to move a service instance from one space to another details
  • Pass through message from broker to client for 409 responses details

UAA and Login

Used Configuration

  • BOSH v117
  • Stemcell v2778
  • CC API v2.19.0

Commit summary.


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

- name: "cf"
  version: "195"
  url: ""
  sha1: "dcdfd2e00e7fc862efae6af212e389067029308d"

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

bosh upload-release --sha1 dcdfd2e00e7fc862efae6af212e389067029308d \