Skip to content

test: Add Ruby3.4 to integ tests #7984

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

Merged
merged 4 commits into from
Apr 26, 2025

Conversation

valerena
Copy link
Contributor

Which issue(s) does this change fix?

Why is this change necessary?

To make sure that Ruby 3.4 is correctly tested in SAM CLI canary tests.

How does it address the issue?

What side effects does this change have?

Mandatory Checklist

PRs will only be reviewed after checklist is complete

  • Add input/output type hints to new functions/methods
  • Write design document if needed (Do I need to write a design document?)
  • Write/update unit tests
  • Write/update integration tests
  • Write/update functional tests if needed
  • make pr passes
  • make update-reproducible-reqs if dependencies were changed
  • Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Also change the runtime of the Ruby `init` template to 3.4 (when the full list
can't be retrieved online)
@valerena valerena requested a review from a team as a code owner April 14, 2025 17:14
@@ -301,7 +308,7 @@ class TestBuildCommand_RubyFunctionsWithGemfileInTheRoot(BuildIntegRubyBase):
This doesn't apply to containerized build, since it copies only the function folder to the container
"""

@parameterized.expand([("ruby3.2"), ("ruby3.3")])
@parameterized.expand([("ruby3.2",), ("ruby3.3",), ("ruby3.4",)])
Copy link
Contributor

Choose a reason for hiding this comment

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

I see we are removing ruby3.2. Should we remove this too?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We're not removing ruby3.2. There are some places where we're changing ruby3.2 to ruby3.4, but very limited. (mostly the default ruby app for sam init when the full json file in the GitHub repo can't be accessed)

Copy link
Member

@roger-zhangg roger-zhangg left a comment

Choose a reason for hiding this comment

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

lgtm

@roger-zhangg roger-zhangg added this pull request to the merge queue Apr 25, 2025
Merged via the queue into aws:develop with commit 820bee5 Apr 26, 2025
50 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants