Stella Yang

Currently, the buildpack does not alert users when there is a significant discrepancy between the specified version range in their configuration and the actual resolved version. This can lead to...

When the `package.json` has invalid content for fields in the engine, the `Checking Node.js version`step of the buildpack throws an error that says `Could not parse package.json. No valid ranges...

When using `docker run`, the default rails app configuration assumes the existence of a `$PORT` environmental variable but does not tell the user that it is required. By making the...

The current buildpack does not provide any warning or acknowledgement when there is a `.ruby-version` file in the root directory. Instead, it solely relies on the Ruby version specified in...

The current buildpack does not warn users when the `Gemfile.lock` lacks a specified Ruby version. This can cause applications to run on a default Ruby version, potentially leading to unexpected...