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 eslint-config-expensify from 2.0.59 to 2.0.73 #821

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

Conversation

MelvinBot
Copy link

snyk-top-banner

Snyk has created this PR to upgrade eslint-config-expensify from 2.0.59 to 2.0.73.

ℹ️ 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 12 versions ahead of your current version.

  • The recommended version was released on a month ago.

Release notes
Package name: eslint-config-expensify from eslint-config-expensify GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • 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 upgrade PRs.

For more information:

Snyk has created this PR to upgrade eslint-config-expensify from 2.0.59 to 2.0.73.

See this package in npm:
eslint-config-expensify

See this project in Snyk:
https://app.snyk.io/org/expensify/project/4945ebcf-d145-4524-893a-d9c905019a72?utm_source=github&utm_medium=referral&page=upgrade-pr
@MelvinBot MelvinBot requested a review from a team as a code owner November 21, 2024 18:49
@melvin-bot melvin-bot bot requested review from aldo-expensify and removed request for a team November 21, 2024 18:49
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