Starting November 3, 2026, adding or updating a payment method on Heroku uses a secure Stripe-hosted page. This change doesn’t affect the existing user experience, or your existing credit cards and invoices.
We have updated the package managers used during the build of Python apps as follows: uv updated from 0.13.4 to 0.13.6 (changelog) And for Cedar-generation Python apps only: Pipenv updated from 2026.10.2 to 2026.10.4 (changelog)
Starting October 16th, Sendgrid rolled out a change that requires Heroku Sendgrid add-on customers create a Sendgrid account to access Sendgrid provisioned from Heroku. See the Sendgrid changelog and documentation for details.
The following PHP extensions have been added or updated: ext-blackfire 2026.10.4 ext-grpc 1.85.0 ext-newrelic 12.12.0.41 The following new Composer versions are now available for use during builds: Composer 2.2.31 Composer 2.11.0 The blackfire CLI agent program used by ext-blackfire has been updated to version 2026.10.2.
Node.js versions 26.13.0 and 24.22.2 have been made available for builds on Heroku. For additional information, please see our article on Node.js Support.
Heroku’s support for Java, Scala, Clojure, and Groovy now uses the following default versions for each supported major version: Java 17 is now 17.0.21.0.3 Java 21 is now 21.0.13.0.3 Java 25 is now 25.0.5.0.3 Java 27 is now 27.0.1.0.3 Please visit the Dev Center for more information on Java version support.
We have updated the heroku-22, heroku-24 and heroku-26 stacks to pick up security and bug fixes in upstream packages. The new base images for each stack will roll out automatically to the Common Runtime over the next 48 hours, followed by Private Spaces. If you use Heroku’s default buildpack-powered build system/stacks, you don’t need to redeploy your app to receive these changes. For Cedar-genera…
Heroku has deprecated support for all Apache Kafka on Heroku instances running on versions 2.8 and 3.7. This deprecation is part of our documented version support policy. Starting today we take action on any remaining clusters on Apache Kafka 2.8 and 3.7 for non-compliance according to our end-of-life policy.
Applications using the heroku/ruby buildpack that do not have a version of Node installed by another buildpack (such as the heroku/nodejs buildpack) will now receive: Node version 24.22.1 These versions and instructions on how to specify a specific version of these binaries can be found on the installed binaries section of the Heroku Ruby Support page.
Python 3.11 is due to reach its scheduled upstream end-of-life in October 2027. In accordance with our Python Version Support Policy, support for Python 3.11 on Heroku is now deprecated. Apps using Python 3.11 will continue to build for now, however, a deprecation warning will be shown in the build log. On 5th January 2028, support for Python 3.11 will be removed from the Python buildpacks. Existi…
Python 3.10 reached its upstream end-of-life on 1st October 2026 and so no longer receives upstream bug or security fixes. In accordance with our Python Version Support Policy, we previously deprecated Python 3.10 support on 21st November 2025 and added a deprecation warning to the build log announcing its end of support. Apps using Python 3.10 will continue to build until 6th January 2027, when s…
Python 3.15.2, 3.14.10, 3.13.18, 3.12.16 and 3.11.18 are now available for use by Python apps on Heroku. See the Python release announcement for details of what changed in these releases. In addition, we have updated the Python 3.15, 3.14, 3.13, 3.12 and 3.11 major version aliases to resolve to these new Python patch versions. We strongly recommend that you use a major version alias when specifyin…
.NET 8.0.133, 8.0.427, 9.0.123, 9.0.320, 10.0.114 and 10.0.403 SDKs have been made available for builds on Heroku. The .NET 8.0 SDKs include .NET Runtime 8.0.33 and ASP.NET Core Runtime 8.0.33. The .NET 9.0 SDKs include .NET Runtime 9.0.22 and ASP.NET Core Runtime 9.0.22. The .NET 10.0 SDKs include .NET Runtime 10.0.14 and ASP.NET Core Runtime 10.0.14. For additional information, please see our ar…
The default Ruby version for new Ruby applications is 3.4.12. You’ll only get the default if the application does not specify a Ruby version. Heroku highly recommends specifying your desired Ruby version. You can specify a Ruby version in your Gemfile: ruby "3.4.12" Once you have a Ruby version specified in your Gemfile, update the Gemfile.lock by running the following command: $ bundle update --r…
Heroku’s support for Java, Scala, Clojure, and Groovy now uses the following default versions for each supported major version: Java 8 is now 1.8.0_512 Java 11 is now 11.0.33 Java 17 is now 17.0.21 Java 21 is now 21.0.13 Java 25 is now 25.0.5 Java 27 is now 27.0.1 Please visit the Dev Center for more information on Java version support.
Ruby v3.4.12 is now available on Heroku. To run your app using this version of Ruby, add the following ruby directive to your Gemfile: ruby "3.4.12" For more information on Ruby 3.4.12, you can view the release announcement.
Ruby v4.0.9 is now available on Heroku. To run your app using this version of Ruby, add the following ruby directive to your Gemfile: ruby "4.0.9" For more information on Ruby 4.0.9, you can view the release announcement.
Ruby v3.3.13 is now available on Heroku. To run your app using this version of Ruby, add the following ruby directive to your Gemfile: ruby "3.3.13" For more information on Ruby 3.3.13, you can view the release announcement.
Ruby v4.0.8 is now available on Heroku. To run your app using this version of Ruby, add the following ruby directive to your Gemfile: ruby "4.0.8" For more information on Ruby 4.0.8, you can view the release announcement.
We have updated the heroku-22, heroku-24 and heroku-26 stacks to pick up security and bug fixes in upstream packages. The new base images for each stack will roll out automatically to the Common Runtime over the next 48 hours, followed by Private Spaces. If you use Heroku’s default buildpack-powered build system/stacks, you don’t need to redeploy your app to receive these changes. For Cedar-genera…
Python 3.15.1, 3.14.9 and 3.13.17 are now available for use by Python apps on Heroku. In addition, we have updated the Python 3.15, 3.14 and 3.13 major version aliases to resolve to these new Python patch versions. We strongly recommend that you use a major version alias when specifying a Python version for your app instead of pinning to an exact patch version, so that your app receives the latest…
We updated the Heroku Platform API schema and reference documentation to include OAuth Session operations. Use this resource and endpoints to list and manage the active OAuth sessions for your user account. New Resource: OAuth Session: Represents a group of OAuth access and refresh tokens for an account. Documented Endpoints: OAuth Session List: Lists OAuth sessions for the authenticated account.…
PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12 fix two critical remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619 (see the PHP security advisory). Redeploy your app to pick up the fixed versions. PHP 8.1 is end-of-life and won’t receive a new release from the PHP project, so PHP 8.1.34 on the Heroku-22 stack has been rebuilt with the PHP project’s backported fix for both vulnerabil…
Node.js versions 26.12.1, 24.22.1, and 22.23.4 have been made available for builds on Heroku. For additional information, please see our article on Node.js Support.
We have updated the package managers used during the build of Python apps as follows: pip updated from 26.2.1 to 26.2.2 (changelog) uv updated from 0.13.1 to 0.13.4 (changelog) And for Cedar-generation Python apps only: Pipenv updated from 2026.9.1 to 2026.10.2 (changelog)
We have updated the heroku-22, heroku-24 and heroku-26 stacks to pick up security and bug fixes in upstream packages. The new base images for each stack will roll out automatically to the Common Runtime over the next 48 hours, followed by Private Spaces. If you use Heroku’s default buildpack-powered build system/stacks, you don’t need to redeploy your app to receive these changes. For Cedar-genera…
We have updated the heroku-22, heroku-24 and heroku-26 stacks to pick up security and bug fixes in upstream packages. The new base images for each stack will roll out automatically to the Common Runtime over the next 48 hours, followed by Private Spaces. If you use Heroku’s default buildpack-powered build system/stacks, you don’t need to redeploy your app to receive these changes. For Cedar-genera…
Go 1.27.3 and 1.26.10 are now available for use by Go apps on Heroku. In addition, we have updated the Go 1.27 and 1.26 version aliases to resolve to these new Go patch versions. See Go Versions for details on how to configure the Go version for your app.
.NET 8.0.132, 8.0.426, 9.0.122, 9.0.319, 10.0.113 and 10.0.402 SDKs have been made available for builds on Heroku. The .NET 8.0 SDKs include .NET Runtime 8.0.32 and ASP.NET Core Runtime 8.0.32. The .NET 9.0 SDKs include .NET Runtime 9.0.21 and ASP.NET Core Runtime 9.0.21. The .NET 10.0 SDKs include .NET Runtime 10.0.13 and ASP.NET Core Runtime 10.0.13. For additional information, please see our ar…
Node.js versions 26.12.0 and 24.22.0 have been made available for builds on Heroku. For additional information, please see our article on Node.js Support.