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

Upgrade to rails 7.0 #22052

Closed
jrafanie opened this issue Aug 12, 2022 · 4 comments
Closed

Upgrade to rails 7.0 #22052

jrafanie opened this issue Aug 12, 2022 · 4 comments

Comments

@jrafanie
Copy link
Member

jrafanie commented Aug 12, 2022

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.

Completed

@jrafanie jrafanie self-assigned this Aug 12, 2022
@kbrock kbrock self-assigned this Aug 17, 2022
@miq-bot miq-bot added the stale label Feb 27, 2023
@miq-bot
Copy link
Member

miq-bot commented Feb 27, 2023

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 master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@kbrock kbrock added pinned and removed stale labels Mar 22, 2023
jrafanie added a commit to jrafanie/manageiq that referenced this issue Dec 4, 2023
jrafanie added a commit to jrafanie/manageiq that referenced this issue Dec 4, 2023
jrafanie added a commit to jrafanie/manageiq that referenced this issue Dec 4, 2023
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 added a commit to jrafanie/manageiq-automation_engine that referenced this issue Dec 4, 2023
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
jrafanie added a commit to jrafanie/manageiq-api that referenced this issue Dec 4, 2023
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
jrafanie added a commit to jrafanie/manageiq-api that referenced this issue Dec 4, 2023
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
jrafanie added a commit to jrafanie/manageiq-automation_engine that referenced this issue Dec 18, 2023
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
jrafanie added a commit to jrafanie/manageiq that referenced this issue Dec 18, 2023
jrafanie added a commit to jrafanie/manageiq that referenced this issue Dec 18, 2023
jrafanie added a commit to jrafanie/manageiq that referenced this issue Dec 18, 2023
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 jrafanie mentioned this issue Feb 1, 2024
3 tasks
@Fryguy Fryguy added this to the Radjabov milestone Feb 21, 2024
@Fryguy Fryguy added this to Roadmap Jun 12, 2024
@Fryguy Fryguy moved this to In progress in Roadmap Jun 12, 2024
@Fryguy
Copy link
Member

Fryguy commented Aug 8, 2024

@jrafanie Is this done? If so can we close and move it to the Radjabov column in the roadmap?

@jrafanie
Copy link
Member Author

jrafanie commented Aug 8, 2024

@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.

@jrafanie
Copy link
Member Author

jrafanie commented Aug 9, 2024

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.

@jrafanie jrafanie closed this as completed Aug 9, 2024
@jrafanie jrafanie moved this from In progress to Radjabov in Roadmap Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Radjabov
Development

No branches or pull requests

4 participants