Ed Morley

> and to avoid disruption when the build time deprecation warning is upgraded to an error in the future. This will be happening within the next couple of weeks in...

> Please migrate to `heroku/builder:22` or `heroku/builder:20`, to continue to receive security updates, and to avoid disruption when the build time deprecation warning is upgraded to an error in the...

It looks like the errors were suppressed for this project in #4420, which is not what I'd recommend. End users need to be made aware of this change, and so...

As of yesterday, the legacy `heroku/buildpacks:20` and `heroku/builder-classic:22` builder images are no longer updated, and so won't receive security updates, fixes or support for new language runtime version releases. Please...

cc @evoxmusic

Gentle nudge that builds using these images will start erroring in the future, plus the underlying images themselves will stop receiving security updates.

@erebe @benjaminch ^

> Gentle nudge that builds using these images will start erroring in the future, plus the underlying images themselves will stop receiving security updates. This will be happening within the...

@benjaminch Ah thank you, I see it happened in: https://github.com/Qovery/engine/commit/9323ce12b4af7936d445b05ef4096511496ec4b2#diff-1d6d87da9c944d92a413b97b36c22686cf328b99b62adacd3a86e2022b4df409R32 Since there was no PR callback reference visible in the history of this issue I hadn't seen the change.

Hi The people who used to maintain this project (one of whom is myself) no longer use it (I work on things other than front-end development now), and no one...