Heroku-20 and Heroku-22 stacks updated

Change effective on 23 May 2024

We have updated the heroku-20 and heroku-22 stacks to pick up security fixes in upstream packages. The new base images for each stack will be rolled out automatically to the Common Runtime over the next 48 hours, followed by Private Spaces.

If you are using Heroku’s default buildpack-powered build system/stacks you do not need to redeploy your app to pick up these changes, since your application’s slug is applied on top of the most recent base image for the stack each time a dyno starts. Currently running dynos will be automatically restarted, so there is no need to manually restart your app.

If your app instead uses Heroku’s container stack (most apps do not), you will need to rebuild your app’s Docker image in order to pick up any updates in the base image specified in your Dockerfile.

See this Dev Center article for an overview of the packages available in each stack’s base image.

Changelog of packages

Stack: heroku-20

  • Added jq version 1.6-1ubuntu0.20.04.1
  • Added libc-ares2 version 1.15.0-1ubuntu0.5
  • Added libjq1 version 1.6-1ubuntu0.20.04.1

Stack: heroku-22

  • Added jq version 1.6-2.1ubuntu3
  • Added libc-ares2 version 1.18.1-1ubuntu0.22.04.3
  • Added libjq1 version 1.6-2.1ubuntu3