Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: changing node support level to min v18 #424

Merged
merged 3 commits into from
Sep 11, 2023

Conversation

nicholasgriffintn
Copy link
Member

@nicholasgriffintn nicholasgriffintn commented Sep 10, 2023

Resolves #413

Description:

As a result of the security support ending for Node v16 on September 11th, this PR sets the minimum supported version for Node to version 18.

After the release of this change, SQS Consumer will only support Node versions 18 and 20.

Type of change:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Why is this change required?:

To ensure that we keep this library secure and at the latest expectations, we only support Node versions that are actively or security release supported.

Code changes:

  • Updated the README
  • Updated the workflows to remove Node 16
  • Updated the Node version in package.json

@codeclimate
Copy link

codeclimate bot commented Sep 10, 2023

Code Climate has analyzed commit a7d0179 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (80% is the threshold).

This pull request will bring the total coverage in the repository to 96.9% (0.0% change).

View more on Code Climate.

@nicholasgriffintn nicholasgriffintn merged commit 4eea14f into main Sep 11, 2023
7 checks passed
@nicholasgriffintn nicholasgriffintn deleted the min-node-18-support branch September 11, 2023 07:29
@github-actions github-actions bot locked and limited conversation to collaborators Sep 11, 2023
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.

Drop support for Node 16
1 participant