Releasesby IbisHeroku-22, Heroku-24 and Heroku-26 stacks updated
Update4 weeks agoUnverifiedAdded Oct 20, 2026
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 .
Topics: Streaming, Security, Observability
More Heroku releases
Every Heroku releaseJRuby version 10.1.2.0 is now available
JRuby v10.1.2.0 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.0", engine: "jruby", engine_version: "10.1.2.0" The JRuby release notes can be found on the JRuby website .
Node.js 26.10.0 is now available
Node.js version 26.10.0 has been made available for builds on Heroku. For additional information, please see our article on Node.js Support .
Ruby version 3.4.11 is now available
Ruby v3.4.11 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.11" For more information on Ruby 3.4.11, you can view the release announcement .
Node.js 22.23.3 is now available
Node.js version 22.23.3 has been made available for builds on Heroku. For additional information, please see our article on Node.js Support .
Node.js 26.9.0 is now available
Node.js version 26.9.0 has been made available for builds on Heroku. For additional information, please see our article on Node.js Support .
PHP updates - September 2026
The following new PHP runtime versions are now available: PHP 8.2.34 PHP 8.3.35 PHP 8.4.26 PHP 8.5.11 The following PHP extensions have been added or updated: ext-blackfire 2026.9.2 ext-grpc 1.84.0 ext-mongodb 1.21.10 ext-mongodb 2.5.3 ext-newrelic 12.11.0.40 ext-phalcon 5.22.0 The Nginx web server has been updated to version 1.30.5 .
OpenJDK 27 is now available for Java, Scala and Clojure apps
Heroku’s support for Java, Scala and Clojure now includes support for OpenJDK version 27. To use this version of OpenJDK, create a system.properties file in your application with the following contents: java.runtime.version=27 After your next deployment, Heroku will install and run your app with OpenJDK 27.
Create and manage OAuth authorizations for a team
Heroku team admins can now create, view, regenerate, and revoke OAuth API authorizations that act on behalf of a team rather than an individual from the Heroku Dashboard and the Heroku CLI . Use team authorizations to grant your team access to the Heroku Platform API . See Team Authorization for more information.
Also shipped on Sep 21, 2026
Heroku in September 2026BigQuery Studio query results pane shows recent run history
The Query results pane now shows a short history of recent runs for a query, including multi-statement queries, without switching to the Job history tab. It is generally available.
The query history system table is now generally available
The system.query.history system table is now generally available. Use it to access account-wide records for queries run on SQL warehouses or serverless compute, including execution status, duration metrics, and query source. See Query history system table reference .
Cortex AI Function Evaluation for measuring quality (Public Preview)
Snowflake Cortex AI Function Evaluation is now available in public preview, enabling customers to measure the output quality, cost, and token usage of custom AI Functions and Cortex AI calls against labeled datasets.
Cortex AI Function Optimization for more efficient AI implementations (Public Preview)
Snowflake Cortex AI Function Optimization is now available in public preview, enabling customers to automatically search across prompts and models for improved implementations of custom AI Functions.
Cortex Agents Compact API (Preview)
The Cortex Agents Compact API is now available in preview. Use the agent:compact endpoint to summarize a conversation and pass the compact representation to subsequent agent:run requests. Compacting conversation history reduces token consumption and helps conversations stay within the model context window.
You can now use the AlloyDB Columnar Engine as a read-optimized, in-memory cache for HNSW vector indexes
You can now use the AlloyDB Columnar Engine as a read-optimized, in-memory cache for HNSW vector indexes. This feature is generally available ( GA ). It accelerates vector search performance and increases queries per second (QPS) for vector workloads. For more information, see Accelerate queries with the Columnar Engine .