From 8b42caf704046f15da50f7fe52e4f52c3384924c Mon Sep 17 00:00:00 2001 From: Ashwin Maroli Date: Mon, 15 Jan 2018 14:40:36 +0530 Subject: [PATCH 1/3] 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..1b35e2edec8 --- /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 + `{% raw %}{% post_url %}{% endraw %}` or `{% raw %}{% link %}{% endraw %}` + 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! From 4547c859dbc8cb41109f74e3fd87ce0441018735 Mon Sep 17 00:00:00 2001 From: Ashwin Maroli Date: Thu, 25 Jan 2018 22:33:53 +0530 Subject: [PATCH 2/3] Update Release Post --- ...md => 2018-01-25-jekyll-3-7-1-released.md} | 49 +++++++++++++------ 1 file changed, 33 insertions(+), 16 deletions(-) rename docs/_posts/{2018-01-15-jekyll-3-7-1-released.md => 2018-01-25-jekyll-3-7-1-released.md} (56%) diff --git a/docs/_posts/2018-01-15-jekyll-3-7-1-released.md b/docs/_posts/2018-01-25-jekyll-3-7-1-released.md similarity index 56% rename from docs/_posts/2018-01-15-jekyll-3-7-1-released.md rename to docs/_posts/2018-01-25-jekyll-3-7-1-released.md index 1b35e2edec8..6467f9ea024 100644 --- a/docs/_posts/2018-01-15-jekyll-3-7-1-released.md +++ b/docs/_posts/2018-01-25-jekyll-3-7-1-released.md @@ -1,6 +1,6 @@ --- title: "Jekyll 3.7.1 Released" -date: 2018-01-15 11:21:00 +0530 +date: 2018-01-25 22:22:22 +0530 author: ashmaroli version: 3.7.1 categories: [release] @@ -10,40 +10,57 @@ 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: +Days later here we're, announcing 3.7.1 that fixes numerous issues! :tada: +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.
+ of the said. + 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.
+ explicitly configures the `scope["path"]` using wildcards. + + Read our [documentation](/docs/configuration/#glob-patterns-in-front-matter-defaults) + 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. + additionally providing us 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.
+ 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.
+ roughly translated to 404 errors on URLs to their posts. + + Props to @localheinz for bringing 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.*
+ 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 `{% raw %}{% post_url %}{% endraw %}` or `{% raw %}{% link %}{% endraw %}` will adapt automatically. + * We also found out that `gem "wdm"` boosts performance while directories are + being watched on Windows. So we recommend having it included in your Gemfile + for a better development experience on Windows. (Newly generated Gemfiles + will hereafter have that gem listed automatically :wink:) + 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. +have been made that should improve your Jekyll experience. All of which, would +not have been possible without our wonderful contributors: + +Alexandr, Andreas Möller, Ashwin Maroli, Chayoung You, Florian Thomas, +Frank Taillandier, Hendrik Schneider, Kacper Duras, Olivia, Parker Moore and +Paul Robert Lloyd. As always, you can see our full changelog on [the History page](/docs/history/). -Happy Jekylling! +Happy Jekylling! :sparkles: From 21b9fa15e7b7af938eebe076ae9b95c4fd3eb865 Mon Sep 17 00:00:00 2001 From: Ashwin Maroli Date: Thu, 25 Jan 2018 22:45:09 +0530 Subject: [PATCH 3/3] correct typo --- docs/_posts/2018-01-25-jekyll-3-7-1-released.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_posts/2018-01-25-jekyll-3-7-1-released.md b/docs/_posts/2018-01-25-jekyll-3-7-1-released.md index 6467f9ea024..fa4f121b4aa 100644 --- a/docs/_posts/2018-01-25-jekyll-3-7-1-released.md +++ b/docs/_posts/2018-01-25-jekyll-3-7-1-released.md @@ -18,7 +18,7 @@ The highlights being: 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. + of the directory. We addressed this by having Jekyll scan the directory path only if the user explicitly configures the `scope["path"]` using wildcards.