Ruby 3.2.2 upgrade #202
Merged
Ruby 3.2.2 upgrade #202
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 8329174. If somehow jobs fail again, I'll stick to using --amend. Whaddya know, it actually happened. Here goes nothing
argvniyx-enroute
force-pushed
the
argv/master/ruby-3-2-2-upgrade
branch
from
d02002c to
ed7f864
Compare
smudge
reviewed
Oct 2, 2023
smudge
requested changes
Oct 2, 2023
Co-authored-by: Nathan Griffith <[email protected]>
betterment-policy-bot-production
bot
dismissed
smudge’s stale review
Invalidated by push of 0868ac1
|
Looks like merging is blocked -- filed an issue since I think this is an error with the branch configs. |
|
@argvniyx-enroute merging is unblocked now, so I'm merging this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
/task https://app.asana.com/0/0/1205605778894636/f
Update
test-trackto use ruby 3.2.2.ruby-versionI had to bump the
nanasess/setup-chromedriveraction step to use v. 117, because 115 was failing (though it was a bit of a cargo cult so do let me know if there's a better way to go about this)Other Information
/domain @Betterment/test_track_core