-
Notifications
You must be signed in to change notification settings - Fork 67
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
Upgrade to Rails 7 #975
Comments
Hi @jim, is this something I could take on? I also volunteer at a tool library and while we don't use circulate, I'm wondering if there's anything I could do to help out :) |
@archonic Sure, if you want to take a stab at it, that would be great! |
Awesome! It looks like the Dockerfile hasn't been updated and seems to have a permissions error when starting. Do you mind if I bring that into a good state too? |
@archonic Not at all - that would be great. I don't use it a ton myself, but I know that some folks do and having it fixed up would be appreciated. I know in the past we used a wrapper script to workaround a permissions issue, perhaps that's not needed anymore? |
I just merged #1134 in case if affects what you're working on 😄 |
@jim All done! Lemme know if it needs any fixing up. I'll be away for a couple weeks after Oct 7th but available after that. |
Fixed by #1178. |
A new version of Rails is out! We'd like to upgrade to it this year now that things are looking pretty stable.
There is a guide to this process that we should be able to follow: https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-6-1-to-rails-7-0
The text was updated successfully, but these errors were encountered: