Update docs link in README.md #598
Merged
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
I'm not sure why the release process isn't producing any docs at `stable` (or, in fact, for any previous versions). In the meantime, it seems better to link users to the dev docs rather than a dead link. FWIW, I had a similar issue in my package some time ago (vtjeng/MIPVerify.jl#116) but it seems to have to do with me using an old version of `Documenter`, which is not the issue you are having here.
|
Indeed I noticed this (I realised it had been broken for years in fact) and I did some things that I hope will produce docs for the next stable release (some v0.22.1). But I did not want to tag the release just for the docs, since I am not sure if what I did will work 😅. Anyways, you are right about pointing to the dev branch of the docs! Thx! |
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.
I'm not sure why the release process isn't producing any docs at
stable(or, in fact, for any previous versions).In the meantime, it seems better to link users to the dev docs rather than a dead link.
FWIW, I had a similar issue in my package some time ago (vtjeng/MIPVerify.jl#116) but it seems to have to do with me using an old version of
Documenter, which is not the issue you are having here.