Updated to Latest jekyll

[johncarl81]

I believe this does the trick, WDYT @mojavelinux #15

[mojavelinux]

Do you think we should lock the versions, at least to the major versions?

[johncarl81]

Although I'm a bit out of my depth here, from my experience with other dependency management systems that may be best. Updated.

[mojavelinux]

@johncarl81 The syntax you have used locks the major version, but not the minor version. In other words, if Jekyll 3.2 is released, then ~> 3.1 will match that.

If we want to also lock the minor version, we need an arbitrary third number. In essence, ~> means allow the last number to increment.

So, to lock to Jekyll 3.1, you'd need to type ~> 3.1.0.

That brings us to the question. Should we lock the minor version too, or just the major version? I'm only asking so we're clear what we are setting.

[johncarl81]

Ah, I should have checked the definition of ~> before making this update. My intention was to lock everything except for the bug-fix portion of the version number. Do you think this is appropriate here?

[mojavelinux]

In that case, we need that extra number. The value doesn't actually matter, so you can just make it "0". It's just a placeholder.

[johncarl81]

Ok, updated.

[mojavelinux]

Let's merge it!

[mojavelinux]

Thanks!