From 697a330818454ea16369d0dba4dff4e7e1e31c04 Mon Sep 17 00:00:00 2001 From: Ashwin Maroli Date: Mon, 15 Jan 2018 14:40:36 +0530 Subject: [PATCH] add release post for v3.7.1 --- .../2018-01-15-jekyll-3-7-1-released.md | 49 +++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 docs/_posts/2018-01-15-jekyll-3-7-1-released.md diff --git a/docs/_posts/2018-01-15-jekyll-3-7-1-released.md b/docs/_posts/2018-01-15-jekyll-3-7-1-released.md new file mode 100644 index 00000000000..0e9c3d4f0c9 --- /dev/null +++ b/docs/_posts/2018-01-15-jekyll-3-7-1-released.md @@ -0,0 +1,49 @@ +--- +title: "Jekyll 3.7.1 Released" +date: 2018-01-15 11:21:00 +0530 +author: ashmaroli +version: 3.7.1 +categories: [release] +--- + +Close on the heels of shipping 3.7.0, we were informed of a couple of +regressions due to the changes made in that release. In due time, Team Jekyll +set out to address those issues as early as possible. + +Days later, here we're announcing 3.7.1 that aims to set things in order. The +highlights being: + + * A major regression in 3.7.0 was that when a Front matter default was + configured with a `scope["path"]` set to a directory, Jekyll would scan + that directory for any subfolders and files, for each document in that + `path`. + Though this is intended, it increases build times in proportion to the size + of the said directory.
+ We addressed this by having Jekyll scan the directory path only if the user + explicitly configures the `scope["path"]` using wildcards. Read our + documentation for more details.
+ A huge shout-out to @mmistakes for bringing this to our notice and + additionally providing with a test repository to aid in resolving the + issue. + * Another regression reported was related to our "Custom collections + directory" feature introduced in 3.7.0.
+ Users setting `collection_dir` to a certain directory would have *altered* + paths to their posts still at the root of their site's source. This + roughly translated to 404 errors on urls to their posts.
+ Props to @localheinz for asserting this regression to our notice.
+ We decided to resolve this by having Jekyll ignore posts and drafts at the + root of the site's source directory if the user customizes the + `collection_dir` setting.
+ Ergo, if you set a custom location for your collections, please ensure you + move all of your collections into that directory. *This includes posts and + drafts as well*. Your links generated by `{% post_url %}` or `{% link %}` + will adapt automatically. + +In addition to the above, numerous other minor fixes and documentation updates +have been made that should improve your Jekyll experience. All of which would +not have been possible without our wonderful contributors: Andreas Möller, +Ashwin Maroli, Florian Thomas, Frank Taillandier, Olivia and Parker Moore. + +As always, you can see our full changelog on [the History page](/docs/history/). + +Happy Jekylling!