This release comes with the following notable changes since v4.3.x:
highlight now allows marking specific lines in the code-block.--livereload-port NUM or via setting desired value to key livereload_port in configuration file.--livereload-ignore or list of paths defined under configuration key
livereload_ignore in order prevent automatic browser-refreshes on change to those paths.base64, csv as
runtime-dependencies. Consequently, those gems will be automatically installed with Jekyll and made available for use
on issuing bundle exec jekyll <command>. Users on older versions of Jekyll will have to manually add the gems to
their Gemfile to resolve dependency errors.json has been added as a runtime-dependency as well to provide consistent behavior across different platforms and
different Ruby versions.mercenary gem has been relaxed to automatically allow future releases.Special thanks to my co-maintainers and members from our community who were instrumental in improving Jekyll codebase, documentation and development workflow since the release of v4.3:
Akira Taguchi, Andy Coates, Daniel Haim, David Silveira, Gabriel B. Nunes, Gaelan Lloyd, Gourav Khunger, IFcoltransG, James Hoctor, Joe Mahoney, Joel Coffman, Jonas Jared Jacek, Jorge, Josh Soref, José Romero, Juan Vásquez, KenHV, Khalila, Koichi ITO, Krisztian Zsolt Sallai, Maciek Palmowski, Mamoru TASAKA, Matt Rogers, Michael Nordmeyer, Mike Slinn, Moncef Belyamani, Muhab Abdelreheem, Olle Jonsson, Olly Headey, Otto Liljalaakso, Parker Moore, QuinnG8, Ram Vasuthevan, Robert Austin, Robert Love, Sean M. Collins, Seth Falco, Seth Louis, Shruti Dalvi, Silent, Simon Wagar, Sutou Kouhei, Tomáš Hübelbauer, Valeriy Van, Virgil Ierubino, Vít Ondruch, William Entriken, William Underwood, a story, halorrr, iulianOnofrei (U-lee-aan), masaki, naoki kodama, nisbet-hubbard, plgagne, velle, waqarnazir, なつき and 林博仁 Buo-ren Lin
Happy Jekyllin’!!
]]>Publishing a small bug-fix release with the following patches:
wdm in Gemfile created by jekyll new.Jekyll::Drops::ThemeDrop#root to render absolute path to theme-gem only if JEKYLL_ENV is explicitly set
to string development.That is all for now. Happy Jekyllin’!!
]]>More details are in the changelog.
Happy Jekylling!
]]>This release, 3.9.4, is to bring Ruby 3.3 support to Jekyll. You can find the details in the changelog.
Happy Jekylling!
]]>This is a very small release containing two things:
logger gem included with that release.Nothing new in the way of features for this release. You’ll need to wait for v4.4 for that. 😄
Happy Jekylling!!
]]>i18n and tzinfo gems. You can now use Jekyll v3.9 with
newer versions of these gems!
More details in the full release notes.
Happy Jekylling!
]]>This is a small release containing fixes for some issues that came to our attention after the release of v4.3.1:
link tag had a significant performance regression with the release of v4.3.0 solely due
to a change related to Jekyll::Site#each_site_file. The new patch restores previous performance
while maintaining the enhancements introduced in v4.3.0.--profile did not stop including the
misleading TOTALS row as advertised in the release-notes for v4.3.0. The row has been removed
completely now.jekyll-sass-converter-3.0.0 that shipped in the interim was not happy with our blank-site
scaffolding (from running jekyll new <path> --blank) having a main.scss stylesheet template
import a Sass partial also named main.scss. So the partial has been renamed to base.scss.That’s about it for this release. Depending on whether you use the features patched in this release, you may either wait for v4.4.0 (releasing in the near future) to update your Gemfile or, download the latest release right away! :)
Happy Jekyllin’!!
]]>sassc for converting your Sass partials and stylesheets into CSS files.
Instead, the converter now uses the sass-embedded gem acting as an interface to Dart Sass, which is the current primary
implementation of Sass under active development. The secondary implementation libsass which the sassc gem interfaced
with has been deprecated by its developers.
However, Dart Sass isn’t fully compatible with older Ruby Sass workflow.
Ruby 2.6.0 (all platforms).3.3.22 (for Linux-based platforms).implmentation OptionIn v3.0.x, sass-embedded is the only supported Sass implmentation, and therefore the config option
sass.implementation introduced in v2.2.0 has been removed.
add_charset OptionThe converter will no longer emit @charset "UTF-8"; or a U+FEFF (byte-order marker) for sassify and scssify
Jekyll filters and hence the redundant option sass.add_charset is no longer active.
line_comments Optionsass-embedded does not support sass.line_comments option.
sass-embedded only allows importing files that have extension names of .sass, .scss or .css. SCSS syntax in
files with .css extension name will result in a syntax error.
In v2.x, the Converter allowed imports using paths relative to site source directory, even if the site source
directory is not present in Sass’ load_paths option. This is a side effect of a bug in the converter, which will remain as is in
v2.x due to its usage in the wild.
In v3.x, imports using paths relative to site source directory will not work out of box. To allow these imports, .
(meaning current directory, or site source directory) need to be explicitly listed under load_paths option.
In v2.x, the Converter allowed imports of files with the same filename as their parent file from sass_dir or
load_paths. This is a side effect of a bug in the Converter, which will remain as is in v2.x due to its usage in the
wild.
In v3.x, imports using the same filename of parent file will create a circular import. To fix such imports, rename
either of the files, or use complete relative path from the parent file.
There are a few intentional behavioral differences between Dart Sass and Ruby Sass. Please refer Behavioral Differences from Ruby Sass for details.
]]>We’re shipping v4.3.1 containing fixes for two issues with v4.3.0:
name attribute for collection documents when accessed in Liquid templates.Thanks to the users who took the time to report the issues to us. Happy Jekyllin’
P.S. Development towards v5 has taken a back seat as of now. I plan on releasing a v4.4.0 instead. That said, please feel free to comment on the tentative roadmap to v5.
]]>