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

Rails 7 & Ruby 3.1 #9328

Closed
wants to merge 28 commits into from
Closed

Rails 7 & Ruby 3.1 #9328

wants to merge 28 commits into from

Conversation

@theforeman-bot
Copy link
Member

Issues: #32685

@ekohl
Copy link
Member Author

ekohl commented Aug 2, 2022

Rebased since some preparation work was merged. No real change compared to the previous version.

My plan is to submit the gem updates after branching, which would give us a much more solid base to work on. Then we can also look at the Zeitwerk changes in more detail.

@theforeman-bot
Copy link
Member

@ekohl, this pull request is currently not mergeable. Please rebase against the develop branch and push again.

If you have a remote called 'upstream' that points to this repository, you can do this by running:

    $ git pull --rebase upstream develop

This message was auto-generated by Foreman's prprocessor

4 similar comments
@theforeman-bot
Copy link
Member

@ekohl, this pull request is currently not mergeable. Please rebase against the develop branch and push again.

If you have a remote called 'upstream' that points to this repository, you can do this by running:

    $ git pull --rebase upstream develop

This message was auto-generated by Foreman's prprocessor

@theforeman-bot
Copy link
Member

@ekohl, this pull request is currently not mergeable. Please rebase against the develop branch and push again.

If you have a remote called 'upstream' that points to this repository, you can do this by running:

    $ git pull --rebase upstream develop

This message was auto-generated by Foreman's prprocessor

@theforeman-bot
Copy link
Member

@ekohl, this pull request is currently not mergeable. Please rebase against the develop branch and push again.

If you have a remote called 'upstream' that points to this repository, you can do this by running:

    $ git pull --rebase upstream develop

This message was auto-generated by Foreman's prprocessor

@theforeman-bot
Copy link
Member

@ekohl, this pull request is currently not mergeable. Please rebase against the develop branch and push again.

If you have a remote called 'upstream' that points to this repository, you can do this by running:

    $ git pull --rebase upstream develop

This message was auto-generated by Foreman's prprocessor

@ekohl
Copy link
Member Author

ekohl commented Sep 28, 2022

This is still not ready for consumption, but since a lot of preparation work has been merged I've rebased this to make the PR a bit easier to grasp.

@ekohl
Copy link
Member Author

ekohl commented Sep 28, 2022

Katello needs to update:

[2022-09-28T09:51:13.727Z] Bundler could not find compatible versions for gem "railties":
[2022-09-28T09:51:13.727Z]   In Gemfile:
[2022-09-28T09:51:13.727Z]     katello was resolved to 4.7.0.pre.master, which depends on
[2022-09-28T09:51:13.727Z]       angular-rails-templates (~> 1.1.0) was resolved to 1.1.0, which depends on
[2022-09-28T09:51:13.727Z]         railties (< 7, >= 4.2)
[2022-09-28T09:51:13.727Z] 
[2022-09-28T09:51:13.727Z]     rails (~> 7.0.3) was resolved to 7.0.3, which depends on
[2022-09-28T09:51:13.727Z]       railties (= 7.0.3)

Version 1.2 of that gem does support Rails 7.

@theforeman-bot
Copy link
Member

Thank you for your contribution, @ekohl! This PR has been inactive for 3 months, closing for now.
Feel free to reopen when you return to it. This is an automated process.

ofedoren and others added 23 commits August 2, 2024 22:54
Currently version 2 is used, but version 3 brings Ruby 3 support.
Version 4 is the latest. The only backwards incompatible changes they
mention[1] are requiring Ruby >= 2.7 and Rails >= 6.0, which is not a
problem for Foreman.

Version 3 enforces that cache_classes is turned off, in particular for
test environments.

[1]: https://github.com/rails/spring/blob/main/CHANGELOG.md
While there is a setting which we change, this allows running with Rails
5+ default settings.
This drops the redirect_back_or_to method that Rails now natively
implements.

It also configures Foreman to raise errors on open redirects, similar to
what was implemented in 2517ba4. Rails
7.0 introduced this as a config option, but only enables it if you load
the 7.0 defaults while after this change it still loads the 6.1
defaults.
@ekohl
Copy link
Member Author

ekohl commented Sep 17, 2024

Closing in favor of #10299.

@ekohl ekohl closed this Sep 17, 2024
@ekohl ekohl deleted the rails-7-ruby-3.1 branch September 17, 2024 12:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants