chore: remove mkdocs polyfill dependency due to security risk#234
Merged
wilsonrljr merged 1 commit intoJun 13, 2026
Merged
Conversation
Up to standards ✅🟢 Issues
|
wilsonrljr
approved these changes
Jun 13, 2026
wilsonrljr
left a comment
wilsonrljr
left a comment
Owner
There was a problem hiding this comment.
Thanks! This looks safe and addresses the polyfill.io security concern. I checked the changed files and it should not conflict with the latest main changes. Approved.
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
2 participants
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.
Description
This PR aims to solve the issue #233 . Due the recent security problems with polyfill and the undesired behaviour on the project documentation, it is better to remove any code using it.