-
Notifications
You must be signed in to change notification settings - Fork 14
Loosen Gemspec to allow Jekyll 3.0 #8
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
base: master
Are you sure you want to change the base?
Conversation
5895ab8 to
f19d727
Compare
|
Updating the build matrix fixed this; I'm happy to use a different set of Ruby versions if you'd prefer. I decided to abandon support for Ruby 1.9.3 since I saw that the core Octopress gem did the same. |
|
This is a big blocker for me. What about Jekyll 3 is making this a hazardous merge to encourage? |
|
@jalcine Also a blocker for me... 8 months later. is anything holding this back? |
|
Any reason why this hasn't been merged? Out of the 12 or so octopress plugins I use, this is the only one that hasn't been updated to allow Jekyll 3.0. |
|
Any reason this can't get updated? |
|
Please merge this |
|
If merging doesn't work for people; y'all can target the fork's repo as well as the SHA/branch it's on. It's shoddy but will work in the interim. |
|
Thanks again for all the hard work of the Octopress team!