Skip to content

build: run the Lambda functions on Node 24 - #215

Merged
hughgrigg merged 1 commit into
mainfrom
build/lambda-node-24
Oct 23, 2026
Merged

hughgrigg merged 1 commit into
mainfrom
build/lambda-node-24

Conversation

@hughgrigg

Copy link
Copy Markdown
Contributor

The three Lambda functions Rainlytics deploys now run on nodejs24.x. They are SummaryFunction, ReportFunction and the report notification publisher (in both its forms, the default code from this package and a site's own entry bundled through NodejsFunction). Node 24 is the newest runtime Lambda supports in production (nodejs26.x is still a preview outside the SLA). A managed runtime in Auto mode takes patch releases itself, so the family is the only thing a construct pins, and the Node 22 family keeps a site's analytics functions behind the rest of its stack. All three handlers are already async, which nodejs24.x requires now that it has dropped callback-style handlers. A site writing its own publisher with reportNotificationHandler gets an async one from that helper.

The package's own Node floor stays at 22. engines, the CI matrix, the getting-started page and the esbuild target for the command line describe the machine a consumer runs CDK and the CLI on, and none of them describes a Lambda runtime.

A site takes the new runtime on its next deploy after upgrading. CloudFormation updates each function in place.

  • Conventional commit message, used as the title
  • Conventional branch name, like feat/concise-description
  • Full check with pnpm run check passed
  • Rebased off latest main
  • User-facing behaviour is documented in docs/

The docs name no Lambda runtime, so nothing there changes.

@coderabbitai ignore

Written by Claude.

nodejs24.x is the newest runtime Lambda supports in production. All three handlers are already async, which it requires.
@hughgrigg
hughgrigg merged commit a6f4407 into main Oct 23, 2026
7 checks passed
@hughgrigg
hughgrigg deleted the build/lambda-node-24 branch October 23, 2026 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants