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
Release v3.7.1 #6695
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. unneccessary use of There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. also: can you replace There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. fair enough! |
||
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. <br /> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
We addressed this by having Jekyll scan the directory path only if the user | ||
explicitly configures the `scope["path"]` using wildcards. <br /> | ||
Read our documentation for more details. <br /> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Link ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Working on a document to attach to the associated PR.. will update after it gets merged.. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are all the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Markdown (or GFM, not sure..) converts There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Link to the docs is still missing here. |
||
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. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
* Another regression reported was related to our "Custom collections | ||
directory" feature introduced in 3.7.0. <br /> | ||
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. <br /> | ||
Props to @localheinz for asserting this regression to our notice. <br /> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i think replacing |
||
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.* <br /> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Moving There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd love it if you can point me to at least one popular plugin that could break.. (not a challenge.., I'd really like to see if there's a workaround / resolution..) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was thinking of paginationv2, jekyll-admin, jekyll-feed to name a few There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. IIRC, |
||
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. | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Update to : Alexandr, Andreas Möller, Ashwin Maroli, Florian Thomas, Frank Taillandier, Kacper Duras, Olivia, Parker Moore, Paul Robert Lloyd |
||
As always, you can see our full changelog on [the History page](/docs/history/). | ||
|
||
Happy Jekylling! |
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.
Link to Jekyll teams ?
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.
I was referring to the team of maintainers instead of a particular team..
so do you want me to link to
affinity-team-captains
here?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.
As Jekyll need more contributors, linking to teams is meant as a way of reminding that people are welcome to join.
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.
isn't
Team Jekyll
meant kind of tongue-in-cheek here? at least that's how i interpreted it, but a link to jekyll teams would be nice, agreedThere 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.
I did not intend it to be
tongue-in-cheek
at all..:I just meant to refer to the maintainers of the codebase without focusing on a particular team or set of individuals..