anchor.diff:      $ git push
       </pre>
   
  -1. Watch the `LANGUAGE-buildpack` pipeline in Concourse. Once the test suite builds pass for the buildpack (the `specs-lts-develop` job and `specs-edge-develop` job), you can mark the Tracker story for the new Dependency release as delivered. Paste links for those successful test suite builds in the Tracker story.
  +1. Monitor the `LANGUAGE-buildpack` pipeline in Concourse. Once the test suite builds, the `specs-lts-develop` job and `specs-edge-develop` job, pass for the buildpack, you can deliver the Tracker story for the new Dependency release. Copy and paste links for the successful test suite builds into the Tracker story.
   
   ##<a id='buildpacks'></a>Buildpacks
   
  
positive.code: 
  ##<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
  * [public-buildpacks-ci-robots](https://github.com/cloudfoundry/public-buildpacks-ci-robots) repo
  * [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 [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>Build the Binaries
  
  
negative.code:         cf_stacks:
            - cflinuxfs2
      ```
      * Follow the current structure of the manifest. For example, if the manifest includes the two most recent patch versions for each minor version of the language, you should also include the two most recent patch versions for each minor version of the language, such as both `ruby-2.1.9` and `ruby-2.1.8`.
      * Copy the `uri` and the `md5` from the `build-BINARY-NAME` job that ran in the Concourse binary-builder pipeline and add them to the manifest.
      <p class="note"><strong>Note</strong>: In the PHP buildpack, you may see a <code>modules</code> line for each PHP dependency in the manifest. Do not include this <code>modules</code> line in your new PHP dependency entry. The <code>modules</code> line will be added to the manifest by the <code>ensure-manifest-has-modules</code> Concourse job in the <code>php-buildpack</code> when you commit and push your changes. You can see this in the output logs of the <code>build-out</code> task.</p>
  
  1. Replace any other mentions of the old version number in the buildpack repository with the new version number. The CF buildpack team uses [Ag](https://github.com/ggreer/the_silver_searcher) for text searching.
  
      <pre class="terminal">$ ag OLD-VERSION</pre>
  
  1. Run the following command to package and upload the buildpack, set up the org and space for tests in the specified CF deployment, and run the CF buildpack tests.
  
      <pre class="terminal">$ BUNDLE_GEMFILE=cf.Gemfile buildpack-build</pre>
  
      If the command fails, you may need to fix or change the tests, fixtures, or other parts of the buildpack.
  
  1. Once the test suite completely passes, use git commands to stage, commit, and push your changes:
  
      <pre class="terminal">
      $ git add .
  