Add Rails 7.1 to the matrix. Also add ruby-head to the matrix.
This was remarkably painful to finish. A small change in the behaviour of rails db:prepare broke our tests, and that sent me off on a adventure through a couple of other PRs that were supposed to help me get the tests running for Rails 7.1, but ended up being a lot of work in themselves. Sigh.
Most of the changes in this PR are files generated by the Rails upgrade of the demo app.
One of the things I tried was simply ignoring the new table, hoping that that would fix (or at least delay) the need to deal with the change to db:prepare, but the model, and therefore the table, is referenced somewhere deep in the Rails initialization code.
Also of note: I don't think anything about Rails 7.1 actually broke the gem. The problems I had or caused myself were because of the way we test the gem.
Add Rails 7.1 to the matrix. Also add
ruby-headto the matrix.This was remarkably painful to finish. A small change in the behaviour of
rails db:preparebroke our tests, and that sent me off on a adventure through a couple of other PRs that were supposed to help me get the tests running for Rails 7.1, but ended up being a lot of work in themselves. Sigh.Most of the changes in this PR are files generated by the Rails upgrade of the demo app.
One of the things I tried was simply ignoring the new table, hoping that that would fix (or at least delay) the need to deal with the change to
db:prepare, but the model, and therefore the table, is referenced somewhere deep in the Rails initialization code.Also of note: I don't think anything about Rails 7.1 actually broke the gem. The problems I had or caused myself were because of the way we test the gem.
I'll do a release to 5.4.0 after merging this PR.