enable 'next' docs for local dev #295
Merged
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
Ethan-Arrowood
approved these changes
Sep 3, 2025
| ``` | ||
|  | ||
|  |
Member
There was a problem hiding this comment.
this concerns me a little bit; what happens when we cut the 4.7 release? Will these images break? Do we have to account for transforming all of these paths?
Member
Author
There was a problem hiding this comment.
4.6 images should always exist. any images added or changed for 4.7 can be put in a 4.7 dir, and so on. the key will be to not delete or change older images so older docs aren't inadvertently modified.
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.
npm startornpm run devwill have acurrentversion using the rootdocsdirnpm run buildwill continue to be a production like build (and will not includenext)