-
Notifications
You must be signed in to change notification settings - Fork 51
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
Moving to Ruby 3.0, Jekyll 4 #862
Comments
Looks like building out side with Ruby 3.1 is now required:
No new webpages until this is fixed. @couet could you please follow what Enrico suggests here and there and see whether that makes things work? It cannot get much more broken than now, so please be courageous. Best would be to rebase our minimal-mistakes commits on top of upstream's master. |
Hi @eguiraud I am running with ruby 3 since a long time and I need to have my now Gemfile to be able to build the web site locally on my machine. My local Gemfile is:
The only difference with the current Gemfile is the line:
I see your proposed GEmfile has more modifications. Are they really needed ? I can build the ROOT website locally with ruby 3 with only this extra line. |
Actually forget my comment, the Gemfile file I have on my Mac book is very close to the one you propose. |
The only difference between your GEmfile and the one I have on my MacBook is the that you changed the line:
By the line
If I do that (use |
On my Mac I have:
And the web site builds fine with the Gemfile posted here: #925 The PR does not work and gives the error:
|
Our website build process depends on the github-pages gem, which does not support Jekyll 4 so we are stuck at Jekyll 3.9, and Jekyll 3.9 does not work with ruby 3, so we are stuck with ruby 2.7.
Ruby 2.7 died 2 months ago.
Building our site with Ruby 3.0 is possible, but we have to drop the dependency on the github-pages gem.
This
Gemfile
works for me with Ruby 3.0.5 and Jekyll 4.3.2 (with the caveat that I have not done extensive testing):There are also a couple of SCSS deprecation warnings but they seem easy to fix.
EDIT:
the warnings are coming from our fork of the minimal-mistakes theme and I fixed them in root-project/minimal-mistakes#22 .
The text was updated successfully, but these errors were encountered: