Skip to content

Comments

[Snyk] Upgrade nodemon from 3.1.4 to 3.1.7#8

Open
9ce59b18 wants to merge 1 commit intomainfrom
snyk-upgrade-ea88ff6c74b2988eb504c33e1fe563b5
Open

[Snyk] Upgrade nodemon from 3.1.4 to 3.1.7#8
9ce59b18 wants to merge 1 commit intomainfrom
snyk-upgrade-ea88ff6c74b2988eb504c33e1fe563b5

Conversation

@9ce59b18
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade nodemon from 3.1.4 to 3.1.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 3 versions ahead of your current version.

  • The recommended version was released on 24 days ago.

Release notes
Package name: nodemon from nodemon 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 nodemon from 3.1.4 to 3.1.7.

See this package in npm:
nodemon

See this project in Snyk:
https://app.snyk.io/org/blausteinstaub/project/63737f80-d6d1-4f26-a350-7cb8cb5cd996?utm_source=github&utm_medium=referral&page=upgrade-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.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

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.

YAML file passed to -w does not trigger restart when it changes config.env should be overridden by runtime env variables

2 participants