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.5.2 #6292
Comments
@parkr fine by me 👍 |
If there's nothing else to add to the release, then I say go for it. 💯
…On Sat, Aug 12, 2017 at 11:21 AM Frank Taillandier ***@***.***> wrote:
@parkr <https://github.com/parkr> fine by me 👍
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#6292 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAEtdh2L1XMyjkUHW03fo0k6XKJ3T-0uks5sXdDugaJpZM4Oz872>
.
|
Well there might be. I could do them in a v3.5.3, or here. I'm considering:
|
isnt #6266 a pretty significant performance boost? let's get at least that in |
Yeah, it is! I'll submit a PR to get that in. |
May as well just do 'em all. |
All tests pass! Releasing... |
Released! I'll get a blog post up momentarily. |
@parkr I just noticed @jekyllbot didn't create the release on GitHub, so I manually added it: https://github.com/jekyll/jekyll/releases |
Oh, weird! Thanks, @DirtyF! |
I'd like to release a PATCH release, v3.5.2, while we work on v3.6.0. It will include:
StaticFile#to_json
toStaticFile#to_liquid
#6302: Backport delegateStaticFile#to_json
toStaticFile#to_liquid
#6273 for v3.5.x: delegateStaticFile#to_json
toStaticFile#to_liquid
Reader#read_directories
: guard against an entry not being a directoryAnything else (small, bug fixes only) you'd like to see included?
/cc @jekyll/affinity-team-captains
The text was updated successfully, but these errors were encountered: