Bump ruby to 2.7.5

[danilobuerger]

Summary

This bumps ruby to the latest 2.7.x versions which includes bug fixes and 3 CVEs (https://www.ruby-lang.org/en/news/2021/11/24/ruby-2-7-5-released/)

Changelog

[iOS] [Changed] - Bump ruby to 2.7.5

Test Plan

no test plan, should just pass tests.

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	7,810,215	+0
android	hermes	armeabi-v7a	7,201,815	+0
android	hermes	x86	8,118,845	+0
android	hermes	x86_64	8,098,971	+0
android	jsc	arm64-v8a	9,643,725	+0
android	jsc	armeabi-v7a	8,417,974	+0
android	jsc	x86	9,592,917	+0
android	jsc	x86_64	10,190,102	+0

Base commit: 184dfb8
Branch: main

[facebook-github-bot]

@GijsWeterings has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[cortinico]

Change looks good but I would hold-on on this till master is green again. @hramos is already aware of it and is looking into it.

Just want to make sure we don't break things even further

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
ios	-	universal	n/a	--

Base commit: 184dfb8
Branch: main

[cortinico]

This time the CI failure is a flaky test so we should be good to go

[facebook-github-bot]

@GijsWeterings has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[danilobuerger]

@cortinico as @mikehardy mentioned in reactwg/react-native-releases#19 (reply in thread) it might be worthwhile to bump straight to the newest version of ruby instead of just the newest in the 2.7 release. What do you think? Are there any internal reasons to stay on 2.7?

[kelset]

I'm trying to learn if from the MSFT side of things we have some specific requirements about Ruby (for now, I couldn't find anything), but in the meantime I'm looking at the Ruby website:

• on the download page, they say current stable is 3.1.1 (https://www.ruby-lang.org/en/downloads/)
• on the maintenance branches one they say that 2.7, 3.0 and 3.1 are all on "normal maintenance" (https://www.ruby-lang.org/en/downloads/branches/)
  So at this point in time it feels like it should be fine to move to 3.1.

But I'm still asking around MSFT internally to learn if there's any reason why we might want to stay on 2.7 so take what I'm saying with a pinch of salt

[cortinico]

@cortinico as @mikehardy mentioned in reactwg/react-native-releases#19 (reply in thread) it might be worthwhile to bump straight to the newest version of ruby instead of just the newest in the 2.7 release. What do you think? Are there any internal reasons to stay on 2.7?

I don't see any blockers on top of my mind. I believe we're good to go, as long as it concerns the iOS build pipeline. I would however suggest we:

1. Merge this PR first.
2. Do the bump to Ruby 3 in a separate PR as see if things are breaking because of that.

The reason is that it might not make it into 0.69.x and I believe we can anyway land this PR regardless 👍

[danilobuerger]

@cortinico Thanks for the feedback. Sounds like a plan.

[react-native-bot]

This pull request was successfully merged by @danilobuerger in 2c87b74.

^{When will my fix make it into a release? | Upcoming Releases}