Heroku Release Notes
73 release notes curated from 74 sources by the Releasebot Team. Last updated: Nov 17, 2026
Heroku Products
- Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
- Modified by Releasebot:Nov 17, 2026
Leiningen 2.13.1 is now the default for Clojure apps
Heroku now builds Clojure apps without a bundled bin/lein script using Leiningen 2.13.1 by default on their next deploy.
Clojure apps on Heroku now build with Leiningen 2.13.1 by default. Apps that don’t include a bin/lein script will use Leiningen 2.13.1 on their next deploy.
For more information on the changes in this release, see the Leiningen release notes. See the Dev Center for more information on setting the Leiningen version.
Original source - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
- Modified by Releasebot:Nov 17, 2026
Clojure CLI 1.12.6.1673 is now the default for Clojure apps
Heroku now builds Clojure apps with Clojure CLI 1.12.6.1673 by default on the next deploy.
Clojure apps on Heroku now build with Clojure CLI 1.12.6.1673 by default. Apps that don’t set CLOJURE_CLI_VERSION will use Clojure CLI 1.12.6.1673 on their next deploy.
For more information on the changes in this release, see the Clojure CLI changelog. See the Dev Center for more information on setting the Clojure CLI version.
Original source All of your release notes in one feed
Join Releasebot and get updates from Heroku and hundreds of other software products.
- Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 12, 2026
Update to default compression algorithm for Heroku Postgres WAL compression
Heroku changes default WAL compression algorithms by Postgres plan, using ztsd on -5 and higher plans and lz4 on -4 and lower.
Change effective on 12 November 2026
We changed the default compression algorithm for the Heroku Data Labs WAL compression feature. The new algorithms are more performant for WAL compression. The default compression algorithm depends on the Heroku Postgres plan:
- Heroku Postgres databases on -5 and higher plans use ztsd.
- Heroku Postgres databases on -4 and lower plans use lz4.
For more information, see Heroku Data Labs: WAL Compression for Postgres Add-ons.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 12, 2026
Migrate classic Heroku Postgres databases to Heroku Postgres Advanced
Heroku now supports migrating classic Postgres databases to Postgres Advanced with a snapshot-based command and optional migration testing.
You can now migrate classic (Standard, Premium, Private, Shield) Heroku Postgres databases to Heroku Postgres Advanced. Use the
heroku data:pg:migratecommand to prepare a source classic database for migration and migrate to a destination Postgres Advanced database. The migration uses a snapshot method to copy the data from your source database to the destination database.See Migrating to Heroku Postgres Advanced for migration instructions and Testing Migrations from Classic Heroku Postgres to Heroku Postgres Advanced for instructions to test the migration beforehand.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 12, 2026
PHP updates - Early November 2026
Heroku updates PHP extensions, adds newer Composer versions, and upgrades Apache and the Blackfire CLI agent.
The following PHP extensions have been added or updated:
- ext-blackfire 2026.11.1
- ext-event 3.2.0
- ext-mongodb 2.5.7
The following new Composer versions are now available for use during builds:
- Composer 2.2.32
- Composer 2.11.2
The Apache HTTP web server has been updated to version 2.4.71.
The blackfire CLI agent program used by ext-blackfire has been updated to version 2026.11.0.
Original source Similar to Heroku with recent updates:
- Smokeball release notes149 release notes · Latest Nov 11, 2026
- Cosmolex release notes20 release notes · Latest Jul 30, 2025
- PracticePanther release notes37 release notes · Latest Oct 27, 2026
- Salesforce release notes101 release notes · Latest Nov 1, 2026
- Microsoft release notes1137 release notes · Latest Nov 13, 2026
- Zoom release notes228 release notes · Latest Nov 14, 2026
- Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 12, 2026
Maven 3.10.0 is now the default Maven version for Java apps
Heroku now builds Java apps with Maven 3.10.0 by default when no Maven Wrapper or version override is configured. Developers can use the Maven Wrapper to pin a version, including Maven 3.9.4, for consistent builds.
Java apps on Heroku now build with Maven 3.10.0 by default. Apps that don’t use the Maven Wrapper and don’t set maven.version in system.properties will use Maven 3.10.0 on their next deploy.
We recommend using the Maven Wrapper to control which Maven version builds your app. Your app then builds with the same Maven version on Heroku as on your local machine. To keep using the previous default, Maven 3.9.4, run this command in the root of your application and add the generated files to your Git repository:
mvn wrapper:wrapper -Dmaven=3.9.4For more information on Maven and its versions, see the Apache Maven documentation. See the Dev Center for more information on specifying a Maven version.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 12, 2026
Ruby apps now default to Node version 26.13.1
Heroku updates the Ruby buildpack to provide Node.js 26.13.1 for applications without Node installed by another buildpack.
Change effective on 12 November 2026
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 26.13.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.
Original source - Nov 11, 2026
- Date parsed from source:Nov 11, 2026
- First seen by Releasebot:Nov 12, 2026
Node.js 26.13.1, 24.22.3, and 22.23.5 now available
Heroku makes Node.js versions 26.13.1, 24.22.3, and 22.23.5 available for builds.
Node.js versions 26.13.1, 24.22.3, and 22.23.5 have been made available for builds on Heroku. For additional information, please see our article on Node.js Support.
Original source - Nov 11, 2026
- Date parsed from source:Nov 11, 2026
- First seen by Releasebot:Nov 12, 2026
.NET file-based apps now default to .NET 11
Heroku now defaults .NET file-based apps without a specified target framework to .NET 11, while preserving explicitly configured frameworks.
Change effective on 11 November 2026
We’ve updated our .NET buildpacks to use .NET 11 (net11.0) by default for file-based apps that don’t specify a target framework.
File-based apps are single .cs source files without a project or solution file. Apps that explicitly set TargetFramework with a #:property directive or Directory.Build.props continue to use that configured target framework.
For example, to target .NET 10:
#:property TargetFramework=net10.0Refer to .NET Behavior in Heroku for more details.
Original source - Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
.NET 8.0.134, 8.0.428, 9.0.124, 9.0.321, 10.0.115, 10.0.404 and 11.0.100 SDKs are now available
Heroku adds updated .NET 8, 9, 10, and 11 SDKs and runtimes for builds.
Change effective on 10 November 2026
.NET 8.0.134, 8.0.428, 9.0.124, 9.0.321, 10.0.115, 10.0.404 and 11.0.100 SDKs have been made available for builds on Heroku.
The .NET 8.0 SDKs include .NET Runtime 8.0.34 and ASP.NET Core Runtime 8.0.34. The .NET 9.0 SDKs include .NET Runtime 9.0.23 and ASP.NET Core Runtime 9.0.23. The .NET 10.0 SDKs include .NET Runtime 10.0.15 and ASP.NET Core Runtime 10.0.15. The .NET 11.0 SDK includes .NET Runtime 11.0.0 and ASP.NET Core Runtime 11.0.0.
For additional information, please see our article on .NET support.
Original source - Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
Go 1.27.4 and 1.26.11 are now available
Heroku now supports Go 1.27.4 and 1.26.11, with version aliases updated to resolve to the latest patch releases.
Go 1.27.4 and 1.26.11 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.
Original source - Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
Changes to when Automated Certificate Management renews certificates
Heroku ACM now uses Let’s Encrypt renewal recommendations to time certificate renewals, including earlier renewals when suggested. The staged rollout requires no action, and current certificates remain active until replacements are ready.
Starting November 16, 2026, Automated Certificate Management (ACM) checks with Let’s Encrypt when to renew each certificate. It uses ACME Renewal Information (ARI), a standard way for Let’s Encrypt to suggest a renewal time for each certificate (RFC 9773). We’re rolling out this change to apps in stages. No action is required.
ACM still renews certificates one month before they expire. If Let’s Encrypt suggests renewing sooner, for example before it revokes certificates, ACM renews in the suggested time. Some certificates renew earlier than before. Each domain keeps serving its current certificate until the new one is ready.
To see when your app’s certificates expire, run the command:
$ heroku certs -a example-appFor more information, see the Certificate Renewal section for ACM.
Original source - Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
Changes to how Automated Certificate Management retries failing certificates
Heroku updates Automated Certificate Management on November 11, 2026, adding a six-hour wait between failed custom-domain renewal checks and stopping attempts after seven days without a valid certificate. Users can correct DNS settings and manually retry with a CLI command.
Starting November 11, 2026, Automated Certificate Management (ACM) changes how it retries certificate renewals for custom domains.
- When a custom domain fails a check, for example because its DNS isn’t set up, ACM waits at least 6 hours before it tries again. To retry sooner, use the heroku certs:auto:refresh command.
- After 7 days without a valid certificate and ACM still can’t issue one, ACM stops trying the domain. It sends a reminder about once a week while the domain stays in this state.
To get a certificate, fix the domain’s setup by pointing it at the DNS target that heroku domains shows. Then, run the command to try again:
$ heroku certs:auto:refresh -a example-appFor each failure reason and how to fix it, see the Troubleshooting section for ACM.
Original source - Nov 9, 2026
- Date parsed from source:Nov 9, 2026
- First seen by Releasebot:Nov 11, 2026
Python 3.15 is now the default Python version
Heroku changes the default Python version for apps without an explicit version to Python 3.15. The update affects Fir apps on their next deployment, while existing Cedar apps remain on their cached major version. Heroku recommends specifying a version in a .python-version file.
Change effective on 09 November 2026
We have changed the default Python version, used by Python apps that do not specify an explicit Python version, from Python 3.14 to Python 3.15.
For Cedar-generation apps this change does not affect existing apps, since the Python classic buildpack pins the Python version to the same major Python version as the previous cached build.
For Fir-generation apps this change will affect both new and existing apps the next time you deploy them, since the Python Cloud Native Buildpack does not pin the Python version on rebuilds.
See What’s New In Python 3.15 to learn more about the new Python version.
We strongly recommend that you specify a Python version for your app in a
Original source.python-versionfile instead of relying on the buildpack’s default Python version. - Nov 9, 2026
- Date parsed from source:Nov 9, 2026
- First seen by Releasebot:Nov 11, 2026
Heroku-22, Heroku-24 and Heroku-26 stacks updated
Heroku updates its heroku-22, heroku-24 and heroku-26 stack base images with upstream security and bug fixes. Updates roll out automatically for standard buildpack apps, while container-stack users need to rebuild their images. Heroku-22 is scheduled to reach end of life in 2027.
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-generation apps, each time a dyno starts, the slug is overlaid on top of the most recent base image. For Fir-generation apps, the built image is rebased on top of the most recent base image.
If your app uses Heroku’s container stack, you must rebuild your app’s Docker image to pick up updates in the base image specified in your Dockerfile.
See this Dev Center article for an overview of the package versions available in each stack’s base image.
The Heroku-22 stack is deprecated and will reach end-of-life on April 30th, 2027. Upgrade to a newer stack as soon as possible. See the Heroku-22 End-Of-Life FAQ for more details.
Changelog of packages
Stack: heroku-22
- Updated apt from version 2.4.14 to 2.4.15ubuntu0.1
- Updated apt-transport-https from version 2.4.14 to 2.4.15ubuntu0.1
- Updated apt-utils from version 2.4.14 to 2.4.15ubuntu0.1
- Updated bind9-dnsutils from version 1:9.18.39-0ubuntu0.22.04.7 to 1:9.18.39-0ubuntu0.22.04.8
- Updated bind9-host from version 1:9.18.39-0ubuntu0.22.04.7 to 1:9.18.39-0ubuntu0.22.04.8
- Updated bind9-libs from version 1:9.18.39-0ubuntu0.22.04.7 to 1:9.18.39-0ubuntu0.22.04.8
- Updated ca-certificates from version 20260816ubuntu0.22.04.1 to 20260816ubuntu0.22.04.2
- Updated ca-certificates-java from version 20190909ubuntu1.3 to 20190909ubuntu1.4
- Updated dnsutils from version 1:9.18.39-0ubuntu0.22.04.7 to 1:9.18.39-0ubuntu0.22.04.8
- Updated libapt-pkg6.0 from version 2.4.14 to 2.4.15ubuntu0.1
- Updated libglib2.0-0 from version 2.72.4-0ubuntu2.10 to 2.72.4-0ubuntu2.11
- Updated libpcre2-8-0 from version 10.39-3ubuntu0.1 to 10.39-3ubuntu0.2
- Updated linux-libc-dev from version 5.15.0-202.212 to 5.15.0-203.213
Updates to packages available at build time only
- Updated libapt-pkg-dev from version 2.4.14 to 2.4.15ubuntu0.1
- Updated libglib2.0-bin from version 2.72.4-0ubuntu2.10 to 2.72.4-0ubuntu2.11
- Updated libglib2.0-data from version 2.72.4-0ubuntu2.10 to 2.72.4-0ubuntu2.11
- Updated libglib2.0-dev from version 2.72.4-0ubuntu2.10 to 2.72.4-0ubuntu2.11
- Updated libglib2.0-dev-bin from version 2.72.4-0ubuntu2.10 to 2.72.4-0ubuntu2.11
- Updated libpcre2-16-0 from version 10.39-3ubuntu0.1 to 10.39-3ubuntu0.2
- Updated libpcre2-32-0 from version 10.39-3ubuntu0.1 to 10.39-3ubuntu0.2
- Updated libpcre2-dev from version 10.39-3ubuntu0.1 to 10.39-3ubuntu0.2
- Updated libpcre2-posix3 from version 10.39-3ubuntu0.1 to 10.39-3ubuntu0.2
Stack: heroku-24
- Updated apt from version 2.8.3 to 2.8.4ubuntu0.1
- Updated bind9-dnsutils from version 1:9.18.39-0ubuntu0.24.04.8 to 1:9.18.39-0ubuntu0.24.04.9
- Updated bind9-host from version 1:9.18.39-0ubuntu0.24.04.8 to 1:9.18.39-0ubuntu0.24.04.9
- Updated bind9-libs from version 1:9.18.39-0ubuntu0.24.04.8 to 1:9.18.39-0ubuntu0.24.04.9
- Updated ca-certificates from version 20260816ubuntu0.24.04.1 to 20260816ubuntu0.24.04.2
- Updated ca-certificates-java from version 20240118 to 20240118ubuntu0.24.04.1
- Updated libapt-pkg6.0t64 from version 2.8.3 to 2.8.4ubuntu0.1
- Updated libpcre2-8-0 from version 10.42-4ubuntu2.1 to 10.42-4ubuntu2.2
- Updated libsqlite3-0 from version 3.45.1-1ubuntu2.8 to 3.45.1-1ubuntu2.9
Updates to packages available at build time only
- Updated libpcre2-16-0 from version 10.42-4ubuntu2.1 to 10.42-4ubuntu2.2
- Updated libpcre2-32-0 from version 10.42-4ubuntu2.1 to 10.42-4ubuntu2.2
- Updated libpcre2-dev from version 10.42-4ubuntu2.1 to 10.42-4ubuntu2.2
- Updated libpcre2-posix3 from version 10.42-4ubuntu2.1 to 10.42-4ubuntu2.2
- Updated linux-libc-dev from version 6.8.0-147.147 to 6.8.0-149.149
Stack: heroku-26
- Updated apt from version 3.2.0 to 3.2.1ubuntu0.1
- Updated base-files from version 14ubuntu6.2 to 14ubuntu6.3
- Updated bind9-dnsutils from version 1:9.20.24-1ubuntu0.4 to 1:9.20.24-1ubuntu0.5
- Updated bind9-host from version 1:9.20.24-1ubuntu0.4 to 1:9.20.24-1ubuntu0.5
- Updated bind9-libs from version 1:9.20.24-1ubuntu0.4 to 1:9.20.24-1ubuntu0.5
- Updated ca-certificates from version 20260816ubuntu0.26.04.1 to 20260816ubuntu0.26.04.2
- Updated ca-certificates-java from version 20260311 to 20260311ubuntu0.26.04.1
- Updated libapt-pkg7.0 from version 3.2.0 to 3.2.1ubuntu0.1
- Updated libpcre2-8-0 from version 10.46-1build1 to 10.46-1ubuntu0.1
Updates to packages available at build time only
- Updated libpcre2-16-0 from version 10.46-1build1 to 10.46-1ubuntu0.1
- Updated libpcre2-32-0 from version 10.46-1build1 to 10.46-1ubuntu0.1
- Updated libpcre2-dev from version 10.46-1build1 to 10.46-1ubuntu0.1
- Updated libpcre2-posix3 from version 10.46-1build1 to 10.46-1ubuntu0.1
- Updated linux-libc-dev from version 7.0.0-42.42 to 7.0.0-43.43
Curated by the Releasebot team
Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.