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 safe_yaml to ~> 1.0.0 #1942
Conversation
Be more strict about what versions we'll take, since this is the stable branch
@@ -29,7 +29,7 @@ Gem::Specification.new do |s| | |||
s.add_runtime_dependency('maruku', "~> 0.7.0") | |||
s.add_runtime_dependency('pygments.rb', "~> 0.5.0") | |||
s.add_runtime_dependency('commander', "~> 4.1.3") | |||
s.add_runtime_dependency('safe_yaml', "~> 0.9.7") | |||
s.add_runtime_dependency('safe_yaml', "~> 1.0.0") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is ~> 1.0
a no-go?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's ~1.0 in master which will download a 1.1 once it's released. I didn't like that idea for a stable branch that's supposed to be relatively stable. So I locked it to 1.0.x. Do we want to let Jekyll 1.x float on safe_yaml 1.x?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as 1.x has 1.8.7 support. 1.0.x is probably safer, so I'm 👍 with it as-is as long as the tests can be fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. Might take a few more days. I have to dust off the VM with 1.8.7 on it.
1.0.x has 1.8.7 support! Ready to ship this. |
✨ ❤️ 🎉 |
Be more strict about what versions we'll take, since this is the stable
branch.
This fixes #1792 for the 1.4.x series of releases.