Repository navigation
Dependency update and protocol option fix - #187
Merged
Merged
Conversation
GumpacG
force-pushed
the
dependency-update
branch
from
September 15, 2026 20:25
5244a41 to
1a3ed2f
Compare
GumpacG
force-pushed
the
dependency-update
branch
from
September 15, 2026 20:31
1a3ed2f to
3a5e161
Compare
xiazcy
approved these changes
Sep 21, 2026
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
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.
Bumps dependencies across the root package, the four templates, and the test harness, and bumps the project version to 2.2.0. Lock files and THIRD_PARTY_LICENSES.txt are regenerated. Node version requirements are unchanged.
Also removes an invalid protocol: 'https' option from the Neptune Analytics Lambda client. Newer AWS SDK versions use config.protocol for the protocol implementation rather than the URL scheme, so passing a string made every query through an Analytics SDK pipeline fail with config.protocol.setSerdeContext is not a function. HTTPS is the default, so the option is redundant. This is independent of the bump: it has been broken since v2.1.0 (#161).
Testing:
The dependency and bump were run against Neptune DB 1.4.7.0 and Neptune Analytics.