docs: use explicit version instead of next tag for typedoc
#4660
Conversation
This file contains hidden or 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
merceyz
changed the title
next tag for typedocnext tag for typedoc
merceyz
force-pushed
the
merceyz/chore/explicit-version
branch
from
fe0cf3d to
eec5f58
Compare
merceyz
force-pushed
the
merceyz/chore/explicit-version
branch
from
eec5f58 to
66c8332
Compare
merceyz
changed the title
next tag for typedocnext tag for typedoc
arcanis
approved these changes
Aug 1, 2022
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.
What's the problem this PR addresses?
We're depending on
typedoc@nextbut that tag doesn't exist anymore.How did you fix it?
Use an explicit version.
Checklist