Release v3.7.0

[parkr]

Hello, maintainers! 👋

By my calculations, it's time for a new release of jekyll. There have been over 100 commits since the last release, v3.6.2.

What else is left to be done before a new release can be made? Please make sure to update History.markdown too if it's not already updated.

Thanks! 💞 ✨

• Do not coerce layout paths in theme-gem to the source directory #6603
• Output correct relative paths to Jekyll's logger #6621
• Write post release (Post: Jekyll 3.7.0 released #6634)

[DirtyF]

👍 We can cut the release soon, only a few remaining PRs for next release

[DirtyF]

@parkr Am I talkin' to you or to @jekyllbot? 😄

[parkr]

@DirtyF @jekyllbot will be the one to open the rest! Just used my token here to test.

We can cut the release right now

As long as there aren't any crazy bugs or usability issues on master (kramdown warnings?), then I'm 👍

[DirtyF]

Did a quick test with jekyll's default site and kramdown warnings are not displayed by default.
So there's not anything blocking us from shipping.

[ghost]

let's ship it now! new year's edition @parkr @DirtyF

[parkr]

👍 Ship at will as long as CI is functioning properly. Let's ship faster next time!