Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade dompurify from 3.0.5 to 3.0.7 #9

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

X-oss-byte
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade dompurify from 3.0.5 to 3.0.7.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released 21 days ago, on 2024-01-04.
Release notes
Package name: dompurify
  • 3.0.7 - 2024-01-04
    • Added better protection against CSPP attacks, thanks @ kevin-mizu
    • Updated browser versions for automated tests
    • Updated Node versions for automated tests
    • Refactored code base, thanks @ ssi02014
    • Refactored build system & deployment, thanks @ ssi02014
  • 3.0.6 - 2023-09-28
    • Refactored the core code-base and several utilities, thanks @ ssi02014
    • Updated and fixed several sections of the README, thanks @ ssi02014
    • Updated several outdated build and test dependencies
  • 3.0.5 - 2023-07-11
    • Fixed a licensing issue spotted and reported by @ george-thomas-hill
    • Updated several build and test dependencies
from dompurify GitHub release notes
Commit messages
Package name: dompurify

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Copy link

stackblitz bot commented Jan 25, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

changeset-bot bot commented Jan 25, 2024

⚠️ No Changeset found

Latest commit: 1161a9d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Type: Enhancement

PR Summary: The pull request upgrades the dompurify package from version 3.0.5 to 3.0.7. This update includes improvements such as better protection against CSPP attacks and refactoring of the code base and build system.

Decision: Comment

📝 Type: 'Enhancement' - not supported yet.
  • Sourcery currently only approves 'Typo fix' PRs.
✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.
No details provided.
✅ Small diff: the diff is small enough to approve with confidence.
No details provided.

General suggestions:

  • Ensure that the upgrade does not introduce any breaking changes that could affect the current functionality of the mermaid package.
  • Verify that all features that rely on dompurify continue to function as expected after the upgrade.
  • Consider performing a thorough dependency audit to ensure that all other dependencies are up-to-date and secure.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

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