Upgrade Redocly & remove unused htmltojsx#3498
Merged
mDuo13 merged 3 commits intotutorials-iav4from Feb 21, 2026
Merged
Conversation
Collaborator
|
npm flags security issues (details below); waiting for Redocly's response. |
Collaborator
Author
|
Switched it to version 0.130.4 now that that version is out and updates |
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
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.
htmltojsxdevDependency that was the source of all the alerts about critical security vulnerabilities. As far as I know we don't actually use it now—Roman had it in the initial version of our Redocly config file, so maybe it was used for some migration scripts or something and it's been carried over unchanged since then, but as far as I can tell nothing references it and nothing broke when I removed it./ja/rippling.html→/ja/docs/concepts/tokens/fungible-tokens/ripplingworks based on the/rippling.html→/docs/concepts/tokens/fungible-tokens/ripplingredirect without needing a separate entry for the Japanese version.)type: 301from the redirects file. This field is optional and the default is 301. I am hoping that by removing this we will have fewer merge conflicts later because the diff won't find "matching" lines in the middle of a change.Tested and working in local dev: