-
Notifications
You must be signed in to change notification settings - Fork 355
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
Support for Jekyll 4.0 #651
Comments
Noteworthy is the upgrade of
|
Can we get an update on this? |
I am also awaiting Jekyll v4.0 support for Github Pages. I need to use the "manually order documents" feature for collections but it is only available in v4.0. https://jekyllrb.com/docs/collections/#manually-ordering-documents |
I'd recommend using GitHub Actions to build your site and publish it on GitHub Pages: https://github.com/BryanSchuetz/jekyll-deploy-gh-pages |
I didn't have any dependency on Jekyll 4.0 except for better SCSS compile performance (due to sassc), but I ditched GitHub Pages in favour of Netlify as it can even install 3rd-party Jekyll plugins which aren't supported by GitHub, and you get all the features that GitHub Pages provides + a few extra for free! |
Please note that Netlify recently limited their free plan to 300min build per month, aka 10min per day. |
In the past, how long did it take for GitHub Pages to update to the latest version of Jekyll? Or is GitHub Pages always on an old Jekyll version? |
I think 10 min per day is sufficient for most users who are using GitHub Pages where they don't update their site as often each day. In my case, I have a moderately complex site with 50+ documents and a handful of 3rd party jekyll plugins and yet the site builds gets published under 40 seconds on Netlify. So hitting that 10 minute limit for the day would be distant. 😅
I think upgrade to 4.0 is going to take some time as it being a major upgrade with 1 breaking change around how |
* Will be updated for github-pages when Jekyll version is bumped up to 4 * github/pages-gem#651
what is the progress for this? Is there support for Jekyll 4? |
As a new user to Jekyll, i am unsure how to post to github pages without the 4.0 support. Would anyone have any suggestions on which previous version i should be using? My bundler says
which doesnt seem right. Regardless, I've given that a try by lowering
Ugh... It would be nice to use |
after a bit of hair pulling, I ACTUALLY read the comments in the
P.S. |
Jekyll 4 has added support for binary operators within BTW @kimchirichie thanks for this comment - that works out on localhost, but unfortunately not on our particular CI/CD setup - so still need a new release of this page. EDIT: Quite a few people asking for it here plus a whole bunch of related questions on Stackoverflow. |
… their titles - NOTE the jekyll `where_exp` filter does not support `and` in 3.8.5 - support has been added in 4.0.0, but cannot upgrade due to `github-pages` gem dependecny - see jekyll/jekyll#6998 - see github/pages-gem#651 (comment)
Not sure if this is any help but I suspect one could do a jekyll 4 build in a github action now. Seems plausible enough to look into whether someone's already done it, in fact. Been trying to make time to give it a shot myself. |
@hoff2-ACN I have built a Theme using Github Pages and Github Actions with the latest Bundler and Jekyll 4.0.0 out of the box, soon will be sharing the tutorial which can be used to deploy your Blog using Jekyll 4 !! 👍 |
@sujaykundu777 fantastic! thank you so much! |
So, with people either going to GitHub Actions or to Netlify, are we to assume that GitHub no longer cares about the traditional write/commit/push-and-publish workflow? This issue has been open well over five months, and four since a committer to this repo (@DirtyF) left a comment. There are clearly a number of people waiting/hoping that one of the very few who are familiar with the codebase (if I'm reading this chart right, about 3 people) can either perform the (apparently non-trivial) updates needed to close this issue or open a PR with enough information for one or more of us tyros to get started. Are we waiting for Godot? |
Disclaimer: I don't work for GitHub, nor am a maintainer for this gem. The update is indeed non-trivial, as there are breaking changes and some impacting issues were raised since Jekyll 4.0 was released, due to the new cache API, so it's safer for GitHub not to upgrade to Jekyll 4.0 for now, as they don't want to break existing websites. As this was already mentioned before, GitHub Actions are the way to go if you want to use a custom Jekyll or plugins at your own risk. I don't have proper rights on this repository, but this issue should be closed for now, as it won't happen anytime soon, no need to give people false hopes. GitHub should come with a proper documentation on how to run Jekyll on GitHub Pages with GitHub Actions. |
Sorry, @DirtyF, I misunderstood your relationship to the project (and possibly GitHub) from the quality of the comments you'd left earlier. Actions sans this Gem sound like The Way Forward for those of us who'd like to take advantage of Jekyll 4 (and future versions). Thanks again. |
On a side note; |
No there is no immediate plants to add Jekyll 4 to this gem. Doing so would require some extensive work in the gem or on the GitHub side to ensure we don't break the millions of Pages sites we build (or have built) with Jekyll 3 up until today. |
- Now taking into account that we use Jekyll 3.9.0 (used by Github Pages) See the following links to get more info on the update: - https://stackoverflow.com/questions/42722902/and-or-on-a-where-exp-expression-on-jekyll - github/pages-gem#651
Would it be possible to opt-in to Jekyll 4, perhaps? Creating a |
This workaround (having to manually specify a `year:` for all entries) is necessary until GitHub Pages updates to Jekyll 4.0+: github/pages-gem#651
Jekyll uses webrick in development mode, and expects it to ship with Ruby. But Ruby 3.0 stopped bundling webrick, which causes an error when you run `jekyll serve` using ruby 3.x. Jekyll 4.3.0—released Oct 2022—adds webrick as a dependency, but GitHub Pages still uses Jekyll 3.9.2 and [has no immediate plans](github/pages-gem#651 (comment)) to upgrade to Jekyll 4. Adding webrick to our Gemfile (per [this thread](jekyll/jekyll#8523)) solves this problem in the meantime.
3.5 years later.... |
I gave up using Jekyll for GitHub Pages since GitHub refuses to support the latest Jekyll version. So I made my own static site generator called genja (https://github.com/wigging/genja). It is a small Python package that you can run from the terminal. Thought I would share it here in case others want to use it. Good luck to everyone else who still uses Jekyll. I'm moving on. Bye 👋 |
@fenixnet-net @wigging everyone is able to build Jekyll sites that aren't stuck using GitHub's gem anymore using the action workflow linked below. https://github.com/actions/starter-workflows/blob/main/pages/jekyll-gh-pages.yml |
@jlosito Yes I know. I don't want to setup a GitHub Action just to build a website. |
@wigging how does your static generator solve deployment problem? Do you mean it will not require to setup CI to publish static pages? |
@limansky Yes, I just build the site locally (on my laptop) and push up the files to the |
@jlosito As @wigging points out, one shouldn't have to set up an entire custom workaround just to use a service github allegedly provides. Jeckyll 4 came out 3.5 years ago. If github was interested in keeping Pages relevant they'd have long since at least published a timeline for implementing the upgrade. To my eyes it looks like this feature is now going to be left to die on the vine, as it were. It's reminiscent of Google Voice - yeah, it's still working, but it's at this point a zombie on a treadmill, shambling forward without going anywhere. |
@wigging Not really, you could use any local version of jekyll you wanted in the same 'build locally then deploy' method that you're now using for your home-grown tool. You just needed to add a .nojekyll file when uploading your assets:
@fenixnet-net They basically have, the modern supported method is 'use the GitHub action'; I suspect they will eventually convert the current legacy system to just be some syntactic sugar on top of GitHub actions, or remove it completely. |
GH Pages deployed without GH Actions seems to be way outdated? github/pages-gem#651 https://github.com/actions/starter-workflows/blob/main/pages/jekyll-gh-pages.yml
|
Jekyll 4.0.0 is out, and brings lots of nice improvements. It would be really nice if
github-pages
gem would add support for Jekyll 4.The text was updated successfully, but these errors were encountered: