This is the first blog post after a year and 11 months since the last time 😛
I had some gotchas when I was working on my project, and I thought it would be good to write a blog post about it. My blog is hosted with GitHub Pages and Jekyll, so I went check it out on GitHub, and saw these alerts.
Oops. OK, gotta fix them first!
Ruby 2.3.2 was still used for the blog. In the near future when Jekyll 4 is officially released, it seems Jekyll requires Ruby 2.4.0 or later. I wanted to install Ruby 2.6.2 for that. Before that, I upgraded rbenv from 1.0.0 to 1.1.2. Then, installed Ruby 2.6.2 with it. And, added
.ruby-versionfile to the blog repo.
It looks like Bundler is pre-installed with the recent Ruby. Nice. Just in case (or more like for my curiosity), I also installed Bundler 2.0.1. According to this Bundler’s guide page, Depending on the declaration in your Gemfile.lock, Bundler version is automatically switched when it runs. Cool.
OK, time to update gems finally. Initially, I just ran
bundle update jekyll, as suggested here. But, I got something like the following error (Forgot to keep the log ¯\_(ツ)_/¯).
json-1.8.3 Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
In Gemfile.lock, json gem was pointed to 1.8.3. Ran
bundle update jsonand it is updated to 1.8.6. Good.
Tried again to update jekyll gem. There was no error. Looks good… except Jekyll itself was not updated ¯\_(ツ)_/¯ Hmm…
I didn’t check Gemfile.lock well, but I retrospectively guess it was because github-pages gem was pointed to 113 in Gemfile.lock. Jekyll is a dependency of the gem.
bundle update github-pages. All dependencies were updated from top to bottom (or inversely? idk). github-pages is version 197, jekyll is 3.7.4, and json dependency are gone (idk why) now!
Made a commit for these changes, and pushed it to the remote on GitHub. Checked Alerts page again, and ta-da, all alerts are gone 🎉
So, that’s pretty much all. And, I haven’t written about something I wanted to blog it yet ¯\_(ツ)_/¯ Well, now I remember how to write a blog post, so all good.
What’s next? Actually, I wanted to update this blog by supporting HTTPS for my own domain. GitHub started supporting it last year. I’ve been wanting to do it. So, it would be the next action item 🔨