Ed Morley

Mozilla's MXR site is down and likely not coming back (see https://bugzilla.mozilla.org/show_bug.cgi?id=1279952). However even when up, it should not be used to pull from as part of a build/automation anyway...

@priya-kinthali Hi! Please could I have a review?

@getup8 Hi! Did you work out why you needed to add `REDIS_CLIENT_KWARGS` too, and not just `CONNECTION_POOL_KWARGS`. From code inspection, it seems that setting the latter on its own should...

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

@dangra @alichay ^

@dangra The differences between the builder images can be seen in the comparison table linked from the OP. Most notable are the `lifecycle` version changes (which impact [supported Buildpack API...

> 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...

> 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...

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...

@Crazybun0422 Have you had a chance to try the above? Also, could you provide more information on when this stopped working? The build log from the last successful build would...