anchor.diff:  
   <strong><%= modified_date %></strong>
   
  -This topic describes how to update the version of an existing dependency in a buildpack.
  -It assumes that you are using a [Concourse](https://concourse.ci) deployment of the [buildpacks-ci](https://github.com/cloudfoundry/buildpacks-ci) pipelines.
  -
  -<p class="note"><strong>Note</strong>: Cloud Foundry does not include release candidates of dependencies in buildpacks.</p>
  -
  -##<a id="notifications"></a>Notifications about New Dependencies
  +This topic describes how to update a dependency in a custom buildpack. These procedures enable Cloud Foundry (CF) operators to maintain custom buildpacks that contain dependencies outside of the dependencies in the CF system buildpacks.
  +
  +##<a id="buildpacks-team"></a>Cloud Foundry Buildpacks Team Process
  +
  +The CF buildpacks team uses the following tools to update dependencies:
  +
  +* A [Concourse](https://concourse.ci) deployment of the [buildpacks-ci](https://github.com/cloudfoundry/buildpacks-ci) pipelines
  +* [Pivotal Tracker](https://www.pivotaltracker.com) for workflow management
  +
  +<p class="note"><strong>Note</strong>: The procedures in this topic refer to the tools used by the CF buildpacks team. However, the procedures do not require the specific tools mentioned above. You can use any CI and workflow management tool to update dependencies in custom buildpacks.</p> 
   
   When the [New Releases](https://buildpacks.ci.cf-app.com/pipelines/notifications/jobs/New%20Releases) job in the [notifications pipeline](https://buildpacks.ci.cf-app.com/pipelines/notifications)
  -detects a new version of a tracked dependency in a buildpack, it creates a [Pivotal Tracker](https://www.pivotaltracker.com) story about building and including the new version of the dependency in the buildpack manifests. It also posts a message as the `dependency-notifier` to the [#buildpacks channel](https://cloudfoundry.slack.com/messages/buildpacks/) in the Cloud Foundry Slack.
  +detects a new version of a tracked dependency in a buildpack, it creates a [Tracker](https://www.pivotaltracker.com) story about building and including the new version of the dependency in the buildpack manifests. It also posts a message as the `dependency-notifier` to the [#buildpacks channel](https://cloudfoundry.slack.com/messages/buildpacks/) in the Cloud Foundry Slack.
   
   ##<a id="building"></a>Building the Binaries
   
  -For all dependencies, you must build the binary from source or acquire the binary as a tarball from a trusted source. For most dependencies, the Cloud Foundry buildpacks team builds the binaries from source.
  +For all dependencies, you must build the binary from source or acquire the binary as a tarball from a trusted source. For most dependencies, the CF buildpacks team builds the binaries from source.
  +
  +<p class="note"><strong>Note</strong>: The steps below assume you are using a Concourse deployment of the <code>buildpacks-ci</code> pipelines and Pivotal Tracker.</p>
   
   To build the binary for a dependency, perform the following steps:
   
  
positive.code: 
  ##<a id='buildpacks'></a>Buildpacks
  
  The following list contains information about the buildpacks maintained by the Cloud Foundry buildpacks team.
  
  ###<a id="build-go-buildpack"></a>Go Buildpack
  
  
negative.code: 1. Pushing your changes triggers the binary building process, which you can  monitor at the [binary-builder pipeline](https://buildpacks.ci.cf-app.com/pipelines/binary-builder)
  of your own `buildpacks-ci` Concourse deployment. When the build completes, it adds a link to the Concourse build run to the Tracker story for the new release. 
  
      <p class="note"><strong>Note</strong>: Binary builds are executed by the CF <a href="https://github.com/cloudfoundry/binary-builder">Binary Builder</a> and the <a href="https://github.com/cloudfoundry/buildpacks-ci/blob/master/pipelines/binary-builder.yml">binary-builder pipeline</a>.</p>
  
  ##<a id="manifest-updates"></a>Updating Buildpack Manifests
  
  After you build the binary for a dependency that you can access and download from a URL, follow these instructions to add the dependency version to the buildpack manifest.
  
  <p class="note"><strong>Note</strong>: The steps below assume you are using a Concourse deployment of the <code>buildpacks-ci</code> pipelines and Pivotal Tracker.</p>
  
  1. Change into the directory of the buildpack for which you want to update dependencies and check out the `develop` branch. 
      <pre class="terminal">
      $ cd ~/workspace/ruby-buildpack
      $ git checkout develop
    </pre>
  
  1. Open the `manifest.yml` for the buildpack and remove or add dependencies.
  