New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v3.7.1 #6695
Merged
Merged
Release v3.7.1 #6695
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
--- | ||
title: "Jekyll 3.7.1 Released" | ||
date: 2018-01-25 22:22:22 +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 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. | ||
|
||
We addressed this by having Jekyll scan the directory path only if the user | ||
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 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. | ||
|
||
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 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. | ||
|
||
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: | ||
|
||
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! :sparkles: |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
of the directory
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops! 😁