In October 2022, a new version 4.3.0
was released. The shipping comes with some really valueable improvements and bug-fixes. The full list of changes are available at the history board of Jekyll Version 4.3.0 if you are interested.
Improvements
Find the most important improvements of the Jekyll engine for version 4.3.0 with the following sections.
Dependencies
-
The Gem webrick is now a listed dependency. You no longer need to add the gem for Webrick to your Gemfile when using Jekyll with Ruby 3.0 or newer.
-
You may now use Rouge v4 or continue using Rouge v3.x by explicitly mentioning the version in your Gemfile.
-
Support for gem tzinfo v2 and non-half-hour offsets have been added.
-
You’ll be able to use v3 of the plugin jekyll-sass-converter
when it ships.
Builds
-
Added support for bundling and loading data files from within a theme-gem similar to existing theme-gem contents.
-
Changes to data files at source will now be respected during incremental builds.
-
site.static_files
now include static files within a collection.
-
You may now configure converters for CSV data.
-
.jekyll-cache
or its equivalent custom cache directory will be automatically ignored by Git.
-
Vendor the current latest mime-types dataset for use with local development server.
Liquid Templates
-
basename
attribute of documents are now exposed to Liquid as name, for example 2022-10-22-jekyll-release-4-3-0.adoc
. Excerpts delegate to associated document attribute.
-
Top-level variable Jekyll::Drops::ThemeDrop
introduced to expose gemspec details of theme-gem (valid only when using theme-gem).
Fixes
Some noteworthy bug-fixes include:
-
Respect BUNDLE_GEMFILE when loading Jekyll plugins via Bundler.
-
Prevent loading versions older than kramdown-2.3.1 as a security measure.
-
Trigger livereloading even if the site has no pages.
-
Ensure the expected class of theme config is returned following a merger.
-
Enable BOM encoding only if configured encoding is UTF-8
.
-
Respect server protocol while injecting livereload script.
-
The table output for --profile
stops printing incorrect TOTALS row.