-
Notifications
You must be signed in to change notification settings - Fork 361
query_map
version mismatch
#471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Ah, I see this will be resolved by #469 ! |
yeah, sorry about that 🤕 |
fixed |
calavera
added a commit
that referenced
this issue
May 6, 2022
If you already have a version of aws_lambda_events in your project, and you update lambda_http, the events package's version might not be updated. This can cause compilation issues like the ones we saw in #471. With this change, the events package will be update with new patch versions, which should prevent issues like that from happening.
2 tasks
calavera
added a commit
that referenced
this issue
May 9, 2022
If you already have a version of aws_lambda_events in your project, and you update lambda_http, the events package's version might not be updated. This can cause compilation issues like the ones we saw in #471. With this change, the events package will be update with new patch versions, which should prevent issues like that from happening.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello! It seems that
aws_lambda_events
has upgraded toquery_map@^0.5
. Aslambda_http
depends on[email protected]
, I'm getting a host of identical compile errors:Cargo.toml
:cargo tree
output:The text was updated successfully, but these errors were encountered: