Skip to content

[Snyk] Security upgrade pino-pretty from 8.1.0 to 10.3.0#25

Open
malhanpraveen wants to merge 1 commit into
masterfrom
snyk-fix-db40545e1948ddf9ef7eeb1a5edfec63
Open

[Snyk] Security upgrade pino-pretty from 8.1.0 to 10.3.0#25
malhanpraveen wants to merge 1 commit into
masterfrom
snyk-fix-db40545e1948ddf9ef7eeb1a5edfec63

Conversation

@malhanpraveen

Copy link
Copy Markdown

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json
  • package-lock.json

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: Medium

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.

@malhanpraveen

Copy link
Copy Markdown
Author

Merge Risk: Medium

This major version upgrade for pino-pretty introduces a significant change in runtime environment support.

Breaking Changes:

  • Node.js Support: Version 10.0.0 and later have dropped support for Node.js versions 14 and 16. Your environment must be running Node.js v18 or newer. [1]
  • Dependency Updates: The upgrade to v9.0.0 included major updates to underlying dependencies like pino itself, which could introduce subtle behavioral changes.

Recommendation:
Verify that your production and development environments are running a supported version of Node.js (v18+). No direct API changes are noted that would require code modification, but testing is recommended due to the major version jump.

Source: GitHub Releases

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