Skip to content

[Snyk] Fix for 1 vulnerabilities#99

Open
davidsuart wants to merge 1 commit into
masterfrom
snyk-fix-181a26e4b9344a398527b806de8f43fc
Open

[Snyk] Fix for 1 vulnerabilities#99
davidsuart wants to merge 1 commit into
masterfrom
snyk-fix-181a26e4b9344a398527b806de8f43fc

Conversation

@davidsuart

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Inefficient Algorithmic Complexity
SNYK-JS-BRACEEXPANSION-17706650
  721  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@davidsuart

Copy link
Copy Markdown
Author

Merge Risk: High

The upgrade of textlint from version 11.9.0 to 14.4.1 is a high-risk change involving three major versions with significant breaking changes. The patch update for @textlint-rule/textlint-rule-no-unmatched-pair is low-risk.

textlint 11.9.0 → 14.4.1 (High Risk)

This upgrade introduces major breaking changes related to the Node.js runtime, core APIs for programmatic use, and module support.

Key Breaking Changes:

  • Node.js Version Requirement: Support for older Node.js versions has been dropped incrementally. textlint v14 requires Node.js 18.14.0 or newer.
  • API Rewrite for ESM Support: To support ESM modules, core APIs have been rewritten. The old APIs like TextLintEngine, TextFixEngine, and TextLintCore are now deprecated and will be removed in future versions. Code using textlint programmatically must be migrated to the new asynchronous APIs like createLinter and loadTextlintrc.
  • CLI Flag Removal: The experimental --parallel and --maxConcurrency flags have been removed in v14.
  • Parser and AST Updates: The internal markdown parser was updated in v12, which may result in new linting errors. Additionally, Abstract Syntax Tree (AST) types were improved in v13, which could affect custom rules.

Recommendation:

  • Update Node.js: Ensure your development and deployment environments are running Node.js 18.14.0 or later.
  • Refactor Programmatic Usage: If you are using textlint as a module, you must refactor your code to replace deprecated APIs (TextLintEngine, TextLintCore, etc.) with the new createLinter API.
  • Review CLI Scripts: Update any build or CI scripts that use the removed --parallel or --maxConcurrency flags.

@textlint-rule/textlint-rule-no-unmatched-pair 1.0.7 → 1.0.8 (Low Risk)

This is a patch version upgrade and is not expected to have any breaking changes.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants