Ed Morley

This was fixed by #143 :-) If you manually set `GIT_EXEC_PATH` as an app config var as a workaround, you can unset it now using: ``` heroku config:unset GIT_EXEC_PATH ```

> This would be a violation of the spec, sort of: (At the risk of being slightly pedantic) Surely the spec only comes into play when actually building a package...

I also think separately this error wording needs updating too: https://github.com/buildpacks/pack/blob/ce8db3c5d11b8e040fd565632668a697e53e4f87/internal/commands/config_trusted_builder.go#L81-L85 (Since it's not only suggested builders that are trusted by default, but any of the "built-in trusted builders")

These docs will also need updating: https://devcenter.heroku.com/articles/django-assets#disabling-collectstatic

Note: In order to make it easier for people to migrate to CNBs, we are also: - Officially supporting an APT style CNB, and committing to ensuring it works with...

It's been a year since the deprecation notice/error was added in #90, and 10 months since we [stopped publishing](https://github.com/heroku/cnb-builder-images/pull/514) new versions of `heroku/buildpacks:20` and `heroku/builder-classic:22` (the last Heroku CNB builder...

An upcoming internal tooling migration with a hard deadline (that will affect the currently running service) means we would need to invest time into this service for it to keep...

We've currently had zero people comment/reach out about the maintenance mode that's been enabled since 1st Oct, and there are no GitHub issue ping-backs, or even any GitHub code/issue search...

We've still had zero concerns/pingbacks/... about the maintenance mode, so tomorrow I'll be beginning the app deletion and sunset.

The staging and prod Heroku apps have now been deleted, along with the rest of the sunset/cleanup steps in internal configs/tools etc.