Skip to content
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

Closed
wants to merge 3 commits into from
Closed

bump dependencies and jekyll version #35

wants to merge 3 commits into from

Conversation

amyspark
Copy link
Contributor

@amyspark amyspark commented Apr 1, 2019

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!

@keithmifsud
Copy link
Owner

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.

@amyspark
Copy link
Contributor Author

amyspark commented Apr 2, 2019

@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?

@keithmifsud
Copy link
Owner

keithmifsud commented Apr 3, 2019 via email

@keithmifsud
Copy link
Owner

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.

@amyspark
Copy link
Contributor Author

amyspark commented Apr 6, 2019

@keithmifsud, it's done!

@cristianocasella
Copy link

sorry, there is any update with this PR?
I would like to update nokogiri on my Jekyll installation to fix this:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11068

Thanks

@kenchan0130
Copy link

@cristianocasella
As this project does not seem to be maintained, I forked this project and started maintenance.
https://github.com/kenchan0130/jekyll-target-blank

I hope it will help you.

@amyspark
Copy link
Contributor Author

Ping @keithmifsud ?

@Krinkle Krinkle mentioned this pull request Oct 5, 2019
@keithmifsud
Copy link
Owner

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?

@keithmifsud
Copy link
Owner

I think I'll release v2.0 for Jekyll 4 as it might not work on older Jekyll's versions.

@keithmifsud keithmifsud self-assigned this Oct 12, 2019
@keithmifsud keithmifsud added this to In progress in Release version 2.0 via automation Oct 12, 2019
@keithmifsud keithmifsud added this to the Release v1.2 || v 2.0 milestone Oct 12, 2019
@keithmifsud
Copy link
Owner

sorry, there is any update with this PR?
I would like to update nokogiri on my Jekyll installation to fix this:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11068

Thanks

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.

keithmifsud added a commit that referenced this pull request Oct 14, 2019
keithmifsud added a commit that referenced this pull request Oct 14, 2019
keithmifsud added a commit that referenced this pull request Oct 14, 2019
@keithmifsud
Copy link
Owner

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.

Release version 2.0 automation moved this from In progress to Done Oct 14, 2019
@kenchan0130
Copy link

@keithmifsud
If you can, I can help you maintain your library.
I continued maintenance here.
I don't want the maintenance to be parallel in multiple repositories.

Please consider my proposal.

@keithmifsud
Copy link
Owner

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!

@keithmifsud
Copy link
Owner

Hi @kenchan0130 , if you submit your PR, I assure that I will look into within 24hrs.

@kenchan0130
Copy link

@keithmifsud I'm relieved to hear that.
I'll move issues and PRs that were coming to my repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging this pull request may close these issues.

None yet

4 participants