chore: upgrade Lambda runtime from nodejs22.x to nodejs24.x #74
No reviewers
Labels
No labels
app
bug
ci
compliance
dependencies
docker
docs
documentation
duplicate
enhancement
good first issue
help wanted
infra
invalid
javascript
question
wontfix
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference: adam/seahaven-slack-bot#74
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "chore/upgrade-nodejs24-lambda-runtime"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Upgrade all nine Lambda
NodejsFunctiondefinitions fromNODEJS_22_XtoNODEJS_24_Xacross the five construct files. Also add dependabot ignores for@types/node >=26to prevent premature major bumps while we remain on thenodejs24.xruntime.Both
package.jsonfiles already carry@types/nodeat^24(root:^24.13.2, socket-mode:^24.0.0) — no pin change was needed.Closes #72
Validation
npm ci— cleantsc --noEmit— zero errorscdk synthblocked by missing Docker daemon in sandbox (OpenSearch CR provider asset); thetscpass confirms allRuntime.NODEJS_24_Xreferences resolve correctlyTests
No automated tests affected. Smoke-testing the real Slack DM bot flows, App Home, WO/PO lookup, and notion-sync is called out as a post-deploy step.
Notes
328440206208/us-east-1and smoke-test before mergeundici— exercise the real Slack round-trip, don't just typecheck✅ Open SWE Review: No issues found
Open SWE reviewed this PR and found no potential bugs to report.
Open in Web