Require 1.20.0 of aws-lambda-go #356
Merged
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
This version has a fix that we need.
MattWhelan
force-pushed
the
mwhelan/lambdaDepFix
branch
from
5694745
to
2f0c15e
Compare
nr-swilloughby
approved these changes
Jun 29, 2022
This was referenced Jun 29, 2022
Merged
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.
This version has a fix that we need.
Links
This PR resolved an issue in AWS's lambda runtime for Go: aws/aws-lambda-go#313
It's present in 1.20.0, and we need that fix, or invocations just timeout.
Details
While that fix happened a long time ago, I was a go novice at the time, and I'm only now figuring out how to get the dependency situation straitened out.