jdx
jdx
I really don't think this is a warning-level issue. If, say, a new version comes out there is no reason to warn the user about that. A setting could be...
we could probably make a `USAGE_BIN` env var or something in order to use allow it to be something else
the trouble is people also need some env vars to be loaded before tools. I wonder if maybe we could use `[env.post]` as a way to mark env vars that...
another idea: ```toml [env] EXAMPLE = {value="{{exec(command='go version')}}", when="after_tools"} ```
you are not using this buildpack (at least, that's not the `heroku` you're running). That message comes from the old Heroku Toolbelt which this buildpack does not use.
The latest version of the Heroku CLI
Just `heroku`. You have the Heroku Toolbelt installed by some other method
do we just need to update cli-engine*?
@ransombriggs once I can get this to pass in appveyor it will fix this problem https://github.com/heroku/heroku-cli/pull/231
love the new output @mmowris, let's work a bit to improve the performance of it though