What happened
AWS Lambda has introduced a public preview track for its managed runtimes, starting with Node.js 26 and Python 3.15. Previously, Lambda runtimes only shipped once a language version reached general availability; now developers can opt into a preview runtime through the Lambda console, CLI, CloudFormation, SAM, or CDK ahead of time. Preview runtimes use the same identifier the eventual GA runtime will use, so a function pinned to nodejs26.x or python3.15 graduates automatically once that version goes GA, with no code changes required.
Why it matters for your business
Teams that want to validate compatibility with an upcoming language runtime — dependency behavior, performance, breaking syntax changes — no longer have to wait for GA and then scramble. The tradeoff is real: preview runtimes are not covered by the Lambda SLA or AWS Support and are explicitly not recommended for production workloads, so this is a testing and feedback channel, not a fast lane to ship on Node 26 or Python 3.15 for anything customer-facing.
What to watch next
Preview runtimes may still take breaking changes before GA, so teams testing now should expect to re-validate once each version ships broadly, and treat any findings as a chance to flag issues to AWS before GA locks behavior in.