-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Upgrade yard to 0.9.12, motivated by CVE. #1938
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
Conversation
I don't know WTF is going on with the build but I don't think it's green on master. |
Rebased on |
Doc diff is 2k+ lines, needs to be closely looked at. |
😬 Can you push the diff up to a branch on rspec/rspec.github.io ? |
@pirj there is a task in the We might need to work on that further to streamline the changes / cleanup the files I'm seeing random ws changes we probably don't need. |
There might be some difference due to:
I'll get back to this a bit later. |
Heh, that might not be relevant :) |
Gemfile
Outdated
@@ -7,7 +7,7 @@ gemspec | |||
rspec_dependencies_gemfile = File.expand_path("../Gemfile-rspec-dependencies", __FILE__) | |||
eval_gemfile rspec_dependencies_gemfile | |||
|
|||
gem 'yard', '~> 0.8.7', require: false | |||
gem 'yard', '~> 0.9.20', :require => false |
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.
I think we can now jump to 0.9.22 :)
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.
Same problem as before though
So the issue is that the diff is too big? I ran the command I didn't specify release tag in Also I may have found a way to get rid of this error #1938 (comment) by installing the gem from |
The diffs are large because they're html and the format will have changed, whats unfortunately needed is to check that our docs are still valid, its probably easier to compare the rendered result than the diff itself... |
I opened a draft PR with the changes. rspec/rspec.github.io#131 As I mentioned in the draft PR. I am wondering if this PR should go to maintenance branch instead of master if we regenerate the documentation. |
For rspec-rails it will need to go to |
e231da0
to
c77cc30
Compare
Closed by #2285 |
No description provided.