feat(maintenance): drop support for Node.js 16.x
Summary
Changes
Please provide a summary of what's being changed
This PR drops support for Node.js 16 for Powertools for AWS Lambda (TypeScript). As discussed in the linked issue, Node.js 16 has reached EOL and its corresponding AWS Lambda managed runtime has been marked as deprecated.
Below a list of changes included in the PR:
- Remove Node.js 16 from test matrixes, test harnesses, scripts, etc.
- Remove deprecated version from docs, comments, issue/PR templates
- Removed deprecation banner from docs, replaced with v1 EOL
- Raised baseline for Layer canary stack to Node.js 18
- Removed
nodejs16xfrom compatible runtimes in Lambda layer - Replaced usage of
Object(someObject).hasOwnProperty(someProperty)withObject.hasOwn(someObject, someProperty)(MDN docs) - Removed polyfill for Error.cause (MDN docs) and
- updated
ParseErrorin Parser utility to use it, as well as every envelope - updated Logger log formatter to assume the option can exist
- Removed conditional behavior around
fetchin e2e tests since now it's present in all supported runtimes
Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed
Issue number: closes #2223
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.
Integration tests on this branch are passing: https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/9757062917
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
1.5% Duplication on New Code