[Snyk] Security upgrade turndown from 5.0.3 to 7.2.2 #3
      
        
          +210
        
        
          −89
        
        
          
        
      
    
  
  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.
  
    
  
    
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonpackage-lock.jsonThis major version upgrade crosses two major versions (v6 and v7) and introduces significant breaking changes.Highlights:Instantiation Change: The most critical change is that the default export is now the TurndownService class. Code must be updated from new turndown() to new TurndownService().Plugin & Option Changes: The turndown-plugin-gfm is now integrated directly and must be enabled via the gfm: true option. Additionally, the remove option has been removed in v6 and requires using custom rules instead.Source: Release notesRecommendation: Developer action is required. You must update how the service is instantiated and review usage of the GFM plugin and element removal options.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-TURNDOWN-12304081
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)