test(integration): drop Node 18 from integration matrix#791
Closed
duncanista wants to merge 1 commit into
Closed
Conversation
AWS deprecated nodejs18.x on Sep 1, 2025, with block-create on Feb 1, 2027. Remove it from the integration test matrix to stop spending ~25% of every CI run on a runtime AWS is winding down. Also delete the orphaned node18 snapshot fixtures so the directory stops accumulating dead files. CI-only change; no customer-facing behavior is affected.
Contributor
Author
|
Closing — dropping Node 18 from the integration test matrix is premature while the library still builds and publishes Node 18 layers ( Will revisit as part of a coordinated Node 18 EOL across the library (stop layer publication + README announcement + drop from CI together). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Drops `nodejs18.x` from the integration test matrix. CI-only change — no customer-facing behavior.
Why
AWS deprecated `nodejs18.x` on Sep 1, 2025:
New ESM/Lambda development is on Node 20/22/24. Keeping Node 18 in CI burned ~25% of every integration-test run on a runtime AWS is winding down.
Changes
Scope intentionally narrow — layer builds, Dockerfile, GitLab pipelines are untouched; those have separate deprecation timelines.
Test plan