You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently ran into a problem when trying to use the heroku based buildpacks where one of their buildpacks didn't define a stacks section in the buildpack.toml file. Kpack says that it's not supported,
message: "validating buildpack heroku procfile@3.1.2: stack heroku-24 is not supported"
In talking with that team, it seems that kpack neesd to be updated to support 0.10 where stacks are optional/deprecated.
This is something we've been meaning to do for a while now and a lot of the work is already in a PR at #1332. But I'm not sure if I (or even @natalieparellano) have the capacity to pick it up again right now.
As @chenbh mentioned, the team has been stretched a bit thin, so it may take some time for someone to get to this. However this does seem to be a relatively "good first issue" if anyone would like to take it on, I am sure a maintainer would be happy to support.
Hello,
I recently ran into a problem when trying to use the heroku based buildpacks where one of their buildpacks didn't define a
stacks
section in the buildpack.toml file. Kpack says that it's not supported,message: "validating buildpack heroku procfile@3.1.2: stack heroku-24 is not supported"
In talking with that team, it seems that kpack neesd to be updated to support 0.10 where
stacks
are optional/deprecated.This came out of this discussion here: heroku/buildpacks-procfile#243
For reference here is when the pack cli fixed it: buildpacks/pack#2047
Yaml
The text was updated successfully, but these errors were encountered: