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

Allow upgrade to rack 3.0 #45741

Closed
wants to merge 2 commits into from
Closed

Allow upgrade to rack 3.0 #45741

wants to merge 2 commits into from

Conversation

ioquatix
Copy link
Contributor

@ioquatix ioquatix commented Aug 3, 2022

Should we add Rack 3 to the text matrix? It's not released yet but will be soon, in the mean time you can get it from git: "https://github.com/rack/rack".

@rails-bot rails-bot bot added the actionpack label Aug 3, 2022
@byroot
Copy link
Member

byroot commented Aug 3, 2022

It's a bit complicated to add another gem version to the "matrix", we test multiple Ruby versions, but not multiple dependency versions.

I'd encourage you to first open a PR that points to rack 3 to see if we can spot some compatibility problems, and if so we'll address them.

@byroot byroot changed the title Work with Rack 3. Allow upgrade to rack 3.0 Aug 3, 2022
@byroot
Copy link
Member

byroot commented Aug 3, 2022

Note to self: CI is failing because bundle lock has to be run. (I'll probably do it tomorrow)

@ioquatix
Copy link
Contributor Author

ioquatix commented Aug 5, 2022

I'd encourage you to first open a PR that points to rack 3 to see if we can spot some compatibility problems, and if so we'll address them.

Do you mind explaining how to do this, because I tried to find a BK pipeline config but couldn't find it. I could not see how to achieve what you are describing, unless you mean add gem "rack", git: ... to the top level gemfile?

@ioquatix
Copy link
Contributor Author

ioquatix commented Aug 5, 2022

cc @tenderlove @jeremyevans

@skipkayhil
Copy link
Member

unless you mean add gem "rack", git: ... to the top level gemfile?

Yeah I think that's what he meant

It's a bit complicated to add another gem version to the "matrix", we test multiple Ruby versions, but not multiple dependency versions.

While complicated, I do think if the plan is to support both versions in the next release we probably want both tested. Maybe running an isolated style suite against each (only on Ruby 3.1) would be sufficient?

https://github.com/rails/buildkite-config Buildkite config is here

@lsylvester
Copy link
Contributor

I have created a branch/PR to resolve the issue with sprockets preventing rack 3 at rails/sprockets#758 - but there appears to be some similar issues with some other test dependencies.

@skipkayhil
Copy link
Member

An alternative to moving rails-ujs out of the repo would be #45546, which could be followed up by removing Blade

@ioquatix
Copy link
Contributor Author

ioquatix commented Dec 5, 2022

Please see #46594 for an updated attempt.

@ioquatix ioquatix closed this Dec 5, 2022
@ioquatix ioquatix deleted the patch-3 branch December 5, 2022 05:27
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.

None yet

4 participants