anchor.diff:  
   ### <a id='release-script'></a> bin/release
   
  -The `release` script provides feedback metadata to <%= vars.product_short %> indicating how the app should be executed. The script is run with one argument, the `build` directory. The script must generate a YAML file in the following format:
  +The `release` script provides feedback metadata to <%= vars.app_runtime_abbr %> indicating how the app should be executed. The script is run with one argument, the `build` directory. The script must generate a YAML file in the following format:
   
   ```
   default_process_types:
  
positive.code: * `bin/detect` determines whether or not to apply the buildpack to an app.
  * `bin/supply` provides dependencies for an app.
  * `bin/finalize` prepares the app for launch.
  * `bin/release` provides feedback metadata to <%= vars.product_short %> indicating how the app should be executed.
  * `bin/compile` is a deprecated alternative to `bin/supply` and `bin/finalize`.
  
  The `bin/supply` and `bin/finalize` scripts replace the deprecated `bin/compile` script. Older buildpacks may still use `bin/compile` with the latest version of <%= vars.product_short %>. In this case, applying multiple buildpacks to a single app is not supported. Similarly, newer buildpacks may still provide `bin/compile` for compatibility with Heroku and older versions of <%= vars.product_short %>.
  
  The `bin/supply` script is required for non-final buildpacks. The `bin/finalize` (or `bin/compile`) script is required for final buildpacks.
  
  
negative.code: owner: Buildpacks
  ---
  
  <% current_page.data.title = "How Buildpacks Work in " + vars.app_runtime_abbr %>
  
  This topic describes how buildpacks are structured and detected in <%= vars.app_runtime_full %> (<%= vars.app_runtime_abbr %>).
  
  
  ## <a id='buildpack-scripts'></a> Buildpack Scripts
  