Ruby `3.x` support
Closed this issue Β· 8 comments
Summary
Ruby 3.x
has been out for more than 2 years now, so I was surprised when I went to run jets new
today and couldn't because there's no support for modern Ruby versions. π
I understand priorities need to be balanced when maintaining a project of this size, but it feels like it's time to bump this one up the list a little if it isn't already on top π Thanks for helping build and maintain this awesome library. I'm excited to see it continue to push Ruby forward in the serverless age.
Main reason Ruby 3 is not supported yet is because AWS Lambda doesnβt support it yet. Itβs a bummer.
RE: Thanks for helping build and maintain this awesome library. I'm excited to see it continue to push Ruby forward in the serverless age.
Thanks for the kind words.
Main reason Ruby 3 is not support yet is because AWS Lambda doesnβt support it yet. Itβs a bummer.
RE: Thanks for helping build and maintain this awesome library. I'm excited to see it continue to push Ruby forward in the serverless age.
Thanks for the kind words.
Thanks for the quick response @tongueroo! Apologies, I did not realize lambda doesn't support 3.x yet π Hopefully this closed issue can serve as an answer to future folks who have this same question at least. ππ»
Seems like this could probably be re-opened with the recent news of container base image support of Ruby 3.2 in Lambda: aws/aws-lambda-base-images#54 (comment)
@Jengah Got me excited. Sadly, its only for the lambda container base image. It's not yet rolled out to AWS Lambda itself officially. The AWS console still shows Ruby 2.7 only.
I checked 2 regions: us-east-1 and us-west-2. Seems like AWS is getting closer ready. Guessing they updated the lambda container image in preparation for it. Will look at adding 3.2 support once it's officially released.
Also, saw that AWS also released python 3.1 recently. So Ruby 3.2 hopefully is close π€
Sorry for the false excitement. As the comment mentions the AWS managed framework runtime should be available within 90 days of the announcement, with 2.7 support lasting 6 months past the General Availability release of the Ruby 3.2 runtime for some roadway to get migrated.
I was more pointing out that preliminary testing could be done using a the supported base container as a custom runtime, but the official managed runtime should be out in the next 60 days or so and may not be worth the effort.
Awesome. Appreciate the heads up!
Done in #654 π Blog Post: Jets v4 Release: Ruby 3.2 Support