Update ex_doc to latest released version (v0.32.1) #238
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Yes, there was a reason: #232 We can retry the new version. |
Sorry I missed that. Do you know if the problem is anything mentioned in https://github.com/elixir-lang/ex_doc/blob/main/CHANGELOG.md? |
|
Thank you. I updated the master branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A change in 08d7fbc downgraded
ex_docfrom v0.31.1 to v0.24.1.That change somehow goes against the trend of previous changes that bumped
ex_doc:Maybe there was a good reason to downgrade, but in any case here's a suggestion to bring back the modern
ex_docexperience for future releases. It worked for me locally to generate docs from the tip of the repo.