Conversation
jlizen
approved these changes
May 7, 2026
Collaborator
|
Maybe let's wait another day on #1136 ? I'm just waiting on push perms on the PR |
2dc255f to
1759d56
Compare
Collaborator
|
@darklight3it fyi the last one i was tracking (#1146 ) just landed |
1759d56 to
77159b4
Compare
jlizen
approved these changes
May 8, 2026
Collaborator
jlizen
left a comment
There was a problem hiding this comment.
lgtm, i agree with the 1.1 -> 1.2 bump over the behavior change on the lambda-http header
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.
🤖 New release
aws_lambda_events: 1.1.3 -> 1.2.0 (✓ API compatible changes)lambda_runtime: 1.1.3 -> 1.2.0 (✓ API compatible changes)lambda_http: 1.1.3 -> 1.2.0 (✓ API compatible changes)Changelog
aws_lambda_eventslambda_runtimelambda_httpThis PR was generated with release-plz.