Skip to content
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

Fix failures against Rails main #1110

Merged
merged 5 commits into from
Aug 10, 2022
Merged

Fix failures against Rails main #1110

merged 5 commits into from
Aug 10, 2022

Conversation

paracycle
Copy link
Member

Motivation

Our builds against Rails main have been failing, so this PR attempts to address all the changes since Rails 7.

Implementation

Each commit explains what was changed with a link to upstream change that made it necessary.

Tests

No additional tests

@paracycle paracycle requested a review from a team as a code owner August 10, 2022 13:17
@paracycle paracycle force-pushed the uk-fix-rails-main-builds branch from ab6e466 to 8f43438 Compare August 10, 2022 13:24
@rafaelfranca
Copy link
Member

CI for all other Rails versions is now broken.

@paracycle paracycle force-pushed the uk-fix-rails-main-builds branch from 8f43438 to 0414b78 Compare August 10, 2022 13:57
@paracycle
Copy link
Member Author

@rafaelfranca Thanks, I missed that the block adding without was for >= 7.0. The with method is only added for >= 7.1.alpha, so I updated that.

`xxx_confirmation` and `xxx_challenge` attributes are added post-Rail 7

Upstream PR: rails/rails#43688
We still need to set the field so that older Rails versions do not
keep showing deprecation warnings like:
```
DEPRECATION WARNING: Using legacy connection handling is deprecated. Please set
`legacy_connection_handling` to `false` in your application.

The new connection handling does not support `connection_handlers`
getter and setter.

Read more about how to migrate at: https://guides.rubyonrails.org/active_record_multiple_databases.html#migrate-to-the-new-connection-handling
```

Upstream removal PR: https://github.com/rails/rails/pull/44827/files
Fixtures no longer eagerly define methods, but instead rely on
`method_missing` to handle fixture methods lazily. Thus, the
implementation needs to change to lookup fixture names in the new
`fixture_sets` class attribute.

Upstream PR: rails/rails#44528
@paracycle paracycle force-pushed the uk-fix-rails-main-builds branch from 0414b78 to 53d3583 Compare August 10, 2022 14:18
@paracycle paracycle enabled auto-merge August 10, 2022 14:32
@paracycle paracycle merged commit 44c80e0 into main Aug 10, 2022
@paracycle paracycle deleted the uk-fix-rails-main-builds branch August 10, 2022 14:34
@paracycle paracycle added bugfix backported Backported to stable branch labels Aug 22, 2022
paracycle added a commit that referenced this pull request Aug 22, 2022
paracycle added a commit that referenced this pull request Aug 22, 2022
paracycle added a commit that referenced this pull request Aug 22, 2022
@shopify-shipit shopify-shipit bot temporarily deployed to production August 31, 2022 14:40 Inactive
@shopify-shipit shopify-shipit bot temporarily deployed to 0-10-stable September 14, 2022 02:35 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backported Backported to stable branch bugfix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants