Skip to content

Ruby 3.4 #4236

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Ruby 3.4 #4236

wants to merge 1 commit into from

Conversation

sethboyles
Copy link
Member

@sethboyles sethboyles commented Feb 26, 2025

Seems like we might have to skip upgrading to Ruby 3.3 because it doesn't look like the default version of Bundler will get the bugfix we need. Trying to upgrade to Ruby 3.4 instead, but am running into more language change issues (particularly around keyword arguments).

We may have to update more fog gems: fog/fog-local#34

capi-release PR: cloudfoundry/capi-release#517

  • I have reviewed the contributing guide

  • I have viewed, signed, and submitted the Contributor License Agreement

  • I have made this pull request to the main branch

  • I have run all the unit tests using bundle exec rake

  • I have run CF Acceptance Tests

Related PRs:

cloudfoundry/capi-release#517
cloudfoundry/capi-dockerfiles#57

@sethboyles sethboyles closed this Feb 26, 2025
@sethboyles sethboyles reopened this Feb 26, 2025
@sethboyles sethboyles marked this pull request as draft February 26, 2025 22:10
@sethboyles sethboyles marked this pull request as ready for review March 27, 2025 22:49
@@ -1,7 +1,7 @@
Sequel.migration do
change do
create_table :asg_timestamps do
primary_key name: :id
primary_key :id, name: :id
Copy link
Member Author

@sethboyles sethboyles Mar 28, 2025

Choose a reason for hiding this comment

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

I think enough time has passed that we don't need to worry about someone having run this migration, but not the followup that corrected it. With Ruby 3.4, this migration would no longer behave consistently, anyway (name: id get serialized to {name: :id} instead of {:name=>:id})

Copy link
Member Author

Choose a reason for hiding this comment

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

I initially tried to make these migrations more explicit, but that caused issues with the rename_column on MySQL 5.7 tests. Which we don't actually support, so a different potential workaround is dropping those tests.

Copy link
Member

Choose a reason for hiding this comment

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

Is it worth just dropping 5.7 from the pipeline then?

* Skipping 3.3 due to bundler bug: rubygems/rubygems#8217
@philippthun
Copy link
Member

@sethboyles On which infrastructure providers did you test this already? You mention in the description possible issues with fog, so I guess we should test this on all the providers we support...

@sethboyles
Copy link
Member Author

@philippthun I only tested on singleton blobstore. The fog-local change ended up being minor, thankfully. But testing on other providers is a good idea... This might be a difficult now that we no longer have the blobstore-fanout, unfortunately.

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.

5 participants