anchor.diff:  
   __Node__: 
   
  -* Verified with: the SHA256 of the `node-vVERSION.tar.gz` file listed on `https://nodejs.org/dist/vVERSION/SHASUMS256.txt` For example, for Node version 4.4.6, the Cloud Foundry buildpacks team verifies with the SHA256 for `node-v4.4.6.tar.gz` on its [SHASUMS256](https://nodejs.org/dist/v4.4.6/SHASUMS256.txt) page.
  +* Verified with: the SHA256 of the `node-vVERSION.tar.gz` file listed on `https://nodejs.org/dist/vVERSION/SHASUMS256.txt` For example, for Node version 4.4.6, the CF buildpacks team verifies with the SHA256 for `node-v4.4.6.tar.gz` on its [SHASUMS256](https://nodejs.org/dist/v4.4.6/SHASUMS256.txt) page.
   * Example: [Enqueuing binary builds for Node 4.4.5 and 6.2.0](https://github.com/cloudfoundry/buildpacks-ci/commit/1747c697dc29db0180253c5d466804784cb3fcce)
   
   ###<a id="build-python-buildpack"></a>Python Buildpack
  
positive.code: 	<pre class="terminal">
  	$ git pull -r
  	</pre>
  1. Locate the YAML file for the buildpack you want to build a binary for. The directory contains YAML files for all the packages and dependencies tracked by the Cloud Foundry buildpacks team. Each YAML file correlates to the build queue for one dependency or package and the naming format is `DEPENDENCY-NAME.yml`. For example, the YAML file tracking the build queue for Ruby is called `ruby-builds.yml` and has the following contents:
  
      ```yaml
      ---
  
negative.code: 
  ##<a id='buildpacks'></a>Buildpacks
  
  The following list contains information about the buildpacks maintained by the CF buildpacks team.
  
  ###<a id="build-go-buildpack"></a>Go Buildpack
  
  