Skip to content

chore: end support for Node.js 16.x#6775

Merged
kuhe merged 7 commits into
aws:mainfrom
siddsriv:node16-deprecation
Jan 6, 2025
Merged

chore: end support for Node.js 16.x#6775
kuhe merged 7 commits into
aws:mainfrom
siddsriv:node16-deprecation

Conversation

@siddsriv
Copy link
Copy Markdown
Contributor

@siddsriv siddsriv commented Jan 3, 2025

Issue

We announced the end of support for Node.js 16.x in the AWS SDK for JavaScript (v3) starting January 6, 2025 back in July, 2024.

Description

Bump engines to node >=18.0.0 in package.json

Testing

How was this change tested?

Additional context

Announcement blog post: https://aws.amazon.com/blogs/developer/announcing-the-end-of-support-for-node-js-16-x-in-the-aws-sdk-for-javascript-v3/


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@siddsriv siddsriv requested a review from a team as a code owner January 3, 2025 21:01
Comment thread clients/client-accessanalyzer/package.json
@kuhe kuhe changed the title feat: end support for Node.js 16.x chore: end support for Node.js 16.x Jan 6, 2025
@siddsriv siddsriv force-pushed the node16-deprecation branch from daa9fe0 to 1293eb6 Compare January 6, 2025 17:07
@kuhe kuhe force-pushed the node16-deprecation branch from 1293eb6 to e2d84c7 Compare January 6, 2025 17:49
@kuhe kuhe merged commit 997e37d into aws:main Jan 6, 2025
@siddsriv siddsriv deleted the node16-deprecation branch January 7, 2025 20:09
@github-actions
Copy link
Copy Markdown

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Jan 22, 2025
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.

3 participants