Update cloudfront invalidation lambda dependencies #461
Conversation
This file contains 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
StepanBrychta
force-pushed
the
Update-npm-dependencies
branch
from
80b41c7 to
1fd927f
Compare
agnesgaroux
approved these changes
Jan 30, 2025
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.
What does this change?
Update npm packages for the
cloudfront/iiif.wellcomecollection.org/edge-lambdaandcloudfront/invalidation/lambdaLambda functions.How to test
Automated testing should be sufficient.
The change only involves updating the
jestpackage to the latest version, and allowing minor version updates of the@aws-sdk/client-s3package.