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 refractor from 3.5.0 to 3.6.0 #7128

Closed

Conversation

JasonStoltz
Copy link
Member

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


Snyk has created this PR to upgrade refractor from 3.5.0 to 3.6.0.

ℹ️ 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 1 version ahead of your current version.
  • The recommended version was released 2 years ago, on 2022-02-25.

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

Snyk has created this PR to upgrade refractor from 3.5.0 to 3.6.0.

See this package in npm:


See this project in Snyk:
https://app.snyk.io/org/eui/project/782ac3a8-8bb4-4658-baa9-190d6cb035f1?utm_source=github-enterprise&utm_medium=referral&page=upgrade-pr
@kibanamachine
Copy link

Preview documentation changes for this PR: https://eui.elastic.co/pr_7128/

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

@cee-chen
Copy link
Contributor

cee-chen commented Oct 26, 2023

Closing in favor of a single PR/changelog #7127

@cee-chen cee-chen closed this Oct 26, 2023
@cee-chen cee-chen deleted the snyk-upgrade-15af101e1d4ae8a666b8fc25c5abafb5 branch November 14, 2023 22:08
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.

5 participants