-
Notifications
You must be signed in to change notification settings - Fork 19
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
bump dependencies and jekyll version #35
Conversation
Hi @amyspark thank you for your contribution 😄 Unfortunately, the build tests are failing and thus I cannot merge the changes. Kindly fix the issues and resubmit. |
@keithmifsud, your .travis.yml asks for bundler v2, but the gemspec uses bundler 1.6. Can I bump the version or should I edit Travis CI to use bundler v1? |
Please bump the version on gemspec so that Travis can test for breaking
changes. Thank you :)
*Keith Mifsud - **Software Engineer*
w: keith-mifsud.me
a: Fastolff House, 30, Regent Street, Great Yarmouth, Norfolk. U.K.
<https://facebook.com/mifsudKeith> <https://twitter.com/keithmifsud>
…On Tue, 2 Apr 2019 at 13:03, L. E. Segovia ***@***.***> wrote:
@keithmifsud <https://github.com/keithmifsud>, your .travis.yml asks for
bundler v2, but the gemspec uses bundler 1.6. Can I bump the version or
should I edit Travis CI to use bundler v1?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB-cCGtqHs1lvuWSODCvbPtGZCkXxgNXks5vc0cdgaJpZM4cWzEG>
.
|
Thanks once again. Sorry to ask, but I am out and cannot pull the PR. Can you please update the version number of this library to 1.1.2? Once done we can merge it. Thank you. |
@keithmifsud, it's done! |
sorry, there is any update with this PR? Thanks |
@cristianocasella I hope it will help you. |
Ping @keithmifsud ? |
Hi @amyspark thank you for your PR... I'm looking into it as we speak :) I really appreciate your help. Sorry I've been away from this library for a while and even Jekyll. Not sure about Jekyll's BC. Should this be a v2 release or just a minor version? |
I think I'll release v2.0 for Jekyll 4 as it might not work on older Jekyll's versions. |
Hi @cristianocasella I will now release v1.2 for the security issue and then 2.0 for Jekyll 4 which will include the security fix. |
Hi @amyspark thanks a lot for your help on this PR :) I moved the cnages to another PR due to some issues with rubocop. I am releasing this now. |
@keithmifsud Please consider my proposal. |
Hi @kenchan0130 Certainly, I think it is a great idea and I greatly appreciate it 😄 I can give you appropriate access, however, we will still require my approval for PRs until we find another suitable contributor. Basically, the aim is to stay in focus with the plugin's intention, maintain the coding standards and also the dev process standards (sem ver etc..). Let me know and thank you once again! |
Hi @kenchan0130 , if you submit your PR, I assure that I will look into within 24hrs. |
@keithmifsud I'm relieved to hear that. |
Hey @keithmifsud , I've bumped this gem's Jekyll version so that it is usable with the alpha of v4. I've also updated nokogiri and bundler.
Let me know if there's any problems!