Pin Jekyll at 3.9

[MichaelCurrin]

trafficstars

Hi, as a low priority idea for you to update your gems. It might not impact you, but locking things down early on can reduce confusion later.

I noticed your Gemfile doesn't pin jekyll, which means you're going to get jekyll 4 installed (if you see the lockfile, this is the case).

For predictability with working on both GitHub Pages and local development, it is best to lock the version in the Gemfile to Jekyll 3.9 as per versions

I recommend using these two lines in Gemfile https://github.com/MichaelCurrin/jekyll-blog-demo/blob/master/Gemfile#L3-L4 (the latter is required explicitly in your file, from Jekyll 3.9)

Then delete Gemfile.lock

Then run

bundle install

And commit the update Gemfile and Gemfile.lock

[MichaelCurrin]

I noticed there is also a GH Actions workflow. That theoretically lets you use Jekyll 4 on GH Pages, but because you just build the site and don't persist the files anywhere like on gh-pages, the workflow doesn't actually act to build the site on GH Pages. It just acts as a CI test.

Also it uses @latest which will be 4 and not 3.