The runtime and server versions supported in a buildpack

Products

• Services Suite

Issue/Introduction

Symptoms:

The buildpacks only support the most recent two versions of the installed dependencies. The applications that are configured to use a fixed dependency eventually run into issues as a buildpack is upgraded. They include newer dependency versions and drop the dependency version required by the applications.

Examples:

• Ruby users who have the specific version of ruby set in their Gemfile
• Node.js users who have the specific version of Node.js set in the package.json file
• PHP users who have the specific version of PHP set in either .bp-config/options.json or in composer.json
• Python users who have the specific version of Python set in runtime.txt
• Go users who have the specific version of Golang set with Godeps

Affected users see an error message like this:

Could not get translated url, exited with: 
DEPENDENCY_MISSING_IN_MANIFEST: https://path/to/ruby-2.1.0.tgz

Environment

Resolution

If an application depends on a binary dependency which is no longer supported:

• Update the application to use a binary dependency that is supported by the buildpack going forward. See the "Additional Information" section below for the details on exactly what each build pack supports.
• For Golang instructions, see this document
• For NodeJS instructions, see this document
• For PHP instructions, see this document
• For Python instructions, see this document
• For Ruby instructions, see this document

2. Use an older version of the buildpack. Pivotal does not recommend this option as using an older version of a buildpack may make it susceptible to know the vulnerabilities that have been patched and fixed in newer versions of the buildpack.