Skip to content
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

0.3 Release #294

Closed
bahildebrand opened this issue Mar 10, 2021 · 8 comments
Closed

0.3 Release #294

bahildebrand opened this issue Mar 10, 2021 · 8 comments
Assignees
Labels
Milestone

Comments

@bahildebrand
Copy link
Contributor

We are currently working towards a 0.3 release for the runtime! There are a few minor changes that need to be made for release, but most of the work is complete. This issue is mostly for tracking the release work that needs to be done.

Please comment here if there are major issues you think should make it into the release.

@bahildebrand bahildebrand added this to the 0.3 milestone Mar 10, 2021
@bahildebrand bahildebrand self-assigned this Mar 10, 2021
@coltonweaver
Copy link
Contributor

Started drafting a release here: https://github.com/awslabs/aws-lambda-rust-runtime/releases

Feel free to edit the changelog as much as you see fit.

@bahildebrand
Copy link
Contributor Author

Made some minor changes, but otherwise I think it looks good.

@Veetaha
Copy link
Contributor

Veetaha commented Mar 10, 2021

Hey guys, that's awesome we've been waiting for it a lot (cc #274). Could you elaborate on what has changed with the maintainership of this repo? Am I right that AWS is dedicating some resources for this repo's support?

@miere
Copy link

miere commented Mar 10, 2021

That’s great news! Is it possible to include one extra tweak in the current lambda-runtime?

I really believe it would be beneficial if we remove the requirement to rewrite our own Error alias for each lambda endpoint. By simply making the existing one public would solve this problem. It would also allow the maintainers to create their own backward compatible Error type, with little to (possibly) zero impact on users of this library.

@bahildebrand
Copy link
Contributor Author

Hey guys, that's awesome we've been waiting for it a lot (cc #274). Could you elaborate on what has changed with the maintainership of this repo? Am I right that AWS is dedicating some resources for this repo's support?

@coltonweaver and I are both maintaining the repo in our free time. Neither of us are on the Lambda team.

That’s great news! Is it possible to include one extra tweak in the current lambda-runtime?

I really believe it would be beneficial if we remove the requirement to rewrite our own Error alias for each lambda endpoint. By simply making the existing one public would solve this problem. It would also allow the maintainers to create their own backward compatible Error type, with little to (possibly) zero impact on users of this library.

This seems like a reasonable request to me. Would you mind opening an issue, and I can take a look tomorrow?

@henriiik
Copy link

henriiik commented Mar 11, 2021

@coltonweaver and I are both maintaining the repo in our free time. Neither of us are on the Lambda team.

@bahildebrand thank you for taking the time to do it! ❤

@brainstorm
Copy link

brainstorm commented Mar 11, 2021

@coltonweaver and I are both maintaining the repo in our free time. Neither of us are on the Lambda team.

@bahildebrand thank you for taking the time to do it! ❤

I second that, looking forward to this release to reboot and extend my project built on top of this lib, kudos! :_)

@bahildebrand
Copy link
Contributor Author

lambda_runtime and lambda_http are both at 0.3.0 on crates.io! The docs are currently in the build queue for docs.rs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants