-
Notifications
You must be signed in to change notification settings - Fork 899
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.0 #22052
Comments
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation. |
Part of the rails 7 upgrade: ManageIQ#22052
Part of the rails 7 upgrade: ManageIQ#22052
We can't dynamically modify the autoload_paths from within the test when zeitwerk is the autoloader. Part of the rails 7 upgrade: ManageIQ#22052
This was only needed for classic autoloader. The core "freedom" patch made zeitwerk autoloader bypass the interlock anyway, so now that we're only supporting zeitwerk, this is no longer needed. Co-dependency: ManageIQ/manageiq#22801 Part of the rails 7 upgrade: ManageIQ/manageiq#22052
This was only needed for classic autoloader. The core "freedom" patch made zeitwerk autoloader bypass the interlock anyway, so now that we're only supporting zeitwerk, this is no longer needed. Co-dependency: ManageIQ/manageiq#22801 Part of the rails 7 upgrade: ManageIQ/manageiq#22052
This was only needed for classic autoloader. The core "freedom" patch made zeitwerk autoloader bypass the interlock anyway, so now that we're only supporting zeitwerk, this is no longer needed. Co-dependency: ManageIQ/manageiq#22801 Part of the rails 7 upgrade: ManageIQ/manageiq#22052
This was only needed for classic autoloader. The core "freedom" patch made zeitwerk autoloader bypass the interlock anyway, so now that we're only supporting zeitwerk, this is no longer needed. Co-dependency: ManageIQ/manageiq#22801 Part of the rails 7 upgrade: ManageIQ/manageiq#22052
Part of the rails 7 upgrade: ManageIQ#22052
Part of the rails 7 upgrade: ManageIQ#22052
We can't dynamically modify the autoload_paths from within the test when zeitwerk is the autoloader. Part of the rails 7 upgrade: ManageIQ#22052
@jrafanie Is this done? If so can we close and move it to the Radjabov column in the roadmap? |
I've been adding bugs to the list so it's all in one place but yes, the feature is done. Maybe once we have smoke test, we can close it for real. |
Let's just close this. I think we should decide to change new schema migrations to use 7.0 when we decide we want to do this. They always keep compatibility with old schema versions so we should upgrade to 7.0 schema for new migrations when we have a feature reason to do so. |
Here's an issue we can link to for all future PRs and work items relating to upgrading to rails 7.
Follow up work now that rails 7 is shipped and 6.1 is dropped - mostly not backward compatible with rails 6.1.
Change default rails version for new schema migrations to rails 7. We'll do this when we need to use a new feature. There is no rush since they keep schema backward compatibity for even EOL rails versions.Completed
The text was updated successfully, but these errors were encountered: