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 is a πββοΈ feature or enhancement.
This is a π§ documentation change.
bundle exec rspec
to verify this)Summary
Add Ruby 3.2 Support to Jets
provided.al2
works with custom ruby runtimes.provided.al2
has the mimimal required packages.Context
3.x
supportΒ #636How to Test
To test Ruby 3.2 support before AWS officially releases the Ruby 3.2 runtime, you can use a custom runtime.
config/application.rb
On your machine, switch ruby 3.2. Example:
Docs: https://rubyonjets.com/docs/extras/custom-runtime/
Version Changes
Major
Upgrading
If you're upgrading from Jets v3 to v4, take a look at the Jets Upgrading Guide. A blue-green deploy is probably required.
What Happens When AWS Releases Ruby 3.2
When AWS releases the official Ruby 3.2 runtime, Jets v4 should support it as-is. You just have to remove the Custom Runtime layer
config.lambda.layers
configuration in config/application.rb andjets deploy
again. That'll swap out the Custom Runtime with the Official Runtime. That's how it's supposed to work πRelated
Blog Post: Jets v4 Release: Ruby 3.2 Support