Skip to content

Update ruby version to support 3.4 Lambda runtime#523

Open
YasserBennani wants to merge 2 commits intomainfrom
update-ruby-3.4
Open

Update ruby version to support 3.4 Lambda runtime#523
YasserBennani wants to merge 2 commits intomainfrom
update-ruby-3.4

Conversation

@YasserBennani
Copy link
Contributor

⚠️ This will be a breaking change, support for Lambda functions running on versions other than Ruby 3.4 will no longer be possible. Please user earlier releases of serverless-tools if still on Ruby 3.2.

@YasserBennani YasserBennani force-pushed the update-ruby-3.4 branch 2 times, most recently from 7e7d058 to 7b84b9e Compare March 12, 2026 12:27
@YasserBennani YasserBennani marked this pull request as ready for review March 12, 2026 15:49
@YasserBennani YasserBennani requested a review from a team as a code owner March 12, 2026 15:49
@YasserBennani YasserBennani requested a review from elipinska March 12, 2026 15:49
mise.toml Outdated
@@ -0,0 +1,3 @@
[tools]
1password = "latest"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this needed?

mise.toml Outdated
@@ -0,0 +1,3 @@
[tools]
1password = "latest"
ruby = "3.4.8"
Copy link
Contributor

@elipinska elipinska Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact, I wonder if we should avoid adding the mise.toml file althogether? Looks like mise supports reading the ruby version from the .ruby-version file: https://mise.jdx.dev/lang/ruby.html#ruby-version-and-gemfile-support

Just conscious that adding mise.toml would mean yet another place that would need to be updated with every version change!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it's not strictly necessary

@elipinska
Copy link
Contributor

elipinska commented Mar 13, 2026

Looks good overall!

Is it worth adding a note about what steps we took to test these changes? I'm thinking it would be a useful reference for ourselves for the future.

I had a look at what non-Data Platform repos use serverless-tools and found these:

  • search-indexing
  • aml-supplier-screening
  • migration-automation
  • dynamic-thumbnail-generator

What are your thoughts on communicating these changes to the owning teams? Is it worth putting some messaging out in addition to the release description?

Update poetry version to 2.2.1 mnatching version currently used on python repos
@YasserBennani
Copy link
Contributor Author

Worth communicating to owners of the other repos 👍

@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants