Skip to content
This repository was archived by the owner on Apr 5, 2025. It is now read-only.

feat(node): add NODEJS_18_X to compatible runtimes #37

Merged
merged 3 commits into from
Mar 6, 2023
Merged

feat(node): add NODEJS_18_X to compatible runtimes #37

merged 3 commits into from
Mar 6, 2023

Conversation

p-mercury
Copy link
Contributor

aws-lambda-powertools-typescript v1.5.1 now supports NODEJS_18_X

aws-lambda-powertools-typescript v1.5.1 now supports NODEJS_18_X
@p-mercury p-mercury changed the title Add NODEJS_18_X to list of compatible runtimes Add NODEJS_18_X to compatible runtimes from 1.0.1 to 1.0.2 Feb 24, 2023
@p-mercury p-mercury changed the title Add NODEJS_18_X to compatible runtimes from 1.0.1 to 1.0.2 feat(node): add NODEJS_18_X to compatible runtimes from 1.0.1 to 1.0.2 Feb 24, 2023
@p-mercury p-mercury changed the title feat(node): add NODEJS_18_X to compatible runtimes from 1.0.1 to 1.0.2 feat(node): add NODEJS_18_X to compatible runtimes Feb 24, 2023
@p-mercury
Copy link
Contributor Author

I’m very sorry, I thought since this was such a small change I wouldn’t need to test it 🫣 but I didn’t realize the aws-cdk-lib was not @latest so the run failed the first two time. I tested my third commit locally, so I should work this time!

@rubenfonseca rubenfonseca merged commit 35e421a into aws-powertools:main Mar 6, 2023
@rubenfonseca
Copy link
Contributor

@p-mercury thank you so much for this!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants