Skip to content

Rails 7.2 upgrade#520

Merged
tsubik merged 5 commits intodevelopfrom
chore/rails-upgrade
Feb 22, 2025
Merged

Rails 7.2 upgrade#520
tsubik merged 5 commits intodevelopfrom
chore/rails-upgrade

Conversation

@tsubik
Copy link
Collaborator

@tsubik tsubik commented Feb 4, 2025

@tsubik tsubik requested a review from santostiago February 4, 2025 12:19
@tsubik tsubik force-pushed the chore/rails-upgrade branch from 96fc45c to 20bdb13 Compare February 20, 2025 18:17
Copy link
Contributor

@santostiago santostiago left a comment

Choose a reason for hiding this comment

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

I approved this without testing. Do you want me to test it?

@tsubik
Copy link
Collaborator Author

tsubik commented Feb 22, 2025

@santostiago the code is on staging for a couple of weeks and there were no Sentry errors reported from that time and everything seems to work just fine.

@tsubik
Copy link
Collaborator Author

tsubik commented Feb 22, 2025

I see one spec is failing after recent dependencies upgrade. I will take a look at that and merge when that is fixed.

@tsubik tsubik force-pushed the chore/rails-upgrade branch from 20bdb13 to 1af54bc Compare February 22, 2025 09:32
Base automatically changed from chore/ruby-upgrade to develop February 22, 2025 09:32
@tsubik tsubik merged commit c966800 into develop Feb 22, 2025
4 checks passed
@tsubik tsubik deleted the chore/rails-upgrade branch February 22, 2025 09:41
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