Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2023

This PR contains the following updates:

Package Change Age Confidence
nodemon (source) ^2.0.4^3.0.0 age confidence

Release Notes

remy/nodemon (nodemon)

v3.1.11

Compare Source

v3.1.10

Compare Source

Bug Fixes

v3.1.9

Compare Source

Bug Fixes
  • maintain backward support for exitcrash (9c9de6e)

v3.1.8

Compare Source

Bug Fixes

v3.1.7

Compare Source

Bug Fixes

v3.1.6

Compare Source

Bug Fixes

v3.1.5

Compare Source

Bug Fixes
  • add missing ignore option to type defintion of config (#​2224) (254c2ab)

v3.1.4

Compare Source

Bug Fixes

v3.1.3

Compare Source

Bug Fixes

v3.1.2

Compare Source

Bug Fixes

v3.1.1

Compare Source

Bug Fixes

v3.1.0

Compare Source

Features

v3.0.3

Compare Source

Bug Fixes

v3.0.2

Compare Source

Bug Fixes

v3.0.1

Compare Source

Bug Fixes

v3.0.0

Compare Source

Bug Fixes
Features
  • always use polling on IBM i (3b58104)
BREAKING CHANGES
  • official support for node@​8 dropped.

However there's no function being used in semver that breaks node 8,
so it's technically still possible to run with node 8, but it will
no longer be supported (or tested in CI).

v2.0.22

Compare Source

Bug Fixes

v2.0.21

Compare Source

Bug Fixes

v2.0.20

Compare Source

Bug Fixes
  • remove postinstall script (e099e91)

v2.0.19

Compare Source

Bug Fixes

v2.0.18

Compare Source

Bug Fixes
  • revert update-notifier forcing esm (1b3bc8c)

v2.0.17

Compare Source

Bug Fixes

v2.0.16

Compare Source

Bug Fixes
  • support windows by using path.delimiter (e26aaa9)

v2.0.15

Compare Source

Bug Fixes

v2.0.14

Compare Source

Bug Fixes

v2.0.13

Compare Source

Bug Fixes

v2.0.12

Compare Source

Bug Fixes

v2.0.11

Compare Source

Bug Fixes
  • ensure numerical OS version check (f523d0e)

v2.0.10

Compare Source

Bug Fixes

v2.0.9

Compare Source

Bug Fixes

v2.0.8

Compare Source

Bug Fixes

v2.0.7

Compare Source

Bug Fixes

v2.0.6

Compare Source

Bug Fixes

v2.0.5

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/nodemon-3.x branch from a1adb7c to 815b77a Compare August 10, 2025 13:37
@renovate renovate bot force-pushed the renovate/nodemon-3.x branch from 815b77a to d3e2377 Compare September 25, 2025 20:09
@renovate renovate bot force-pushed the renovate/nodemon-3.x branch from d3e2377 to 9987dce Compare October 22, 2025 01:45
@renovate renovate bot force-pushed the renovate/nodemon-3.x branch from 9987dce to be92ea5 Compare November 11, 2025 17:44
@renovate renovate bot force-pushed the renovate/nodemon-3.x branch from be92ea5 to d2f5d3d Compare December 31, 2025 17:50
@renovate renovate bot force-pushed the renovate/nodemon-3.x branch from d2f5d3d to 56f53c6 Compare January 8, 2026 18:47
@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
Critical CVE: npm apidoc-core has a prototype pollution vulnerability

CVE: GHSA-6vj3-p34w-xxjp apidoc-core has a prototype pollution vulnerability (CRITICAL)

Affected versions: >= 0.2.0 <= 0.15.0

Patched version: No patched versions

From: ?npm/apidoc@0.25.0npm/apidoc-core@0.12.0

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/apidoc-core@0.12.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Critical
Critical CVE: npm flat vulnerable to Prototype Pollution

CVE: GHSA-2j2x-2gpw-g8fm flat vulnerable to Prototype Pollution (CRITICAL)

Affected versions: < 5.0.1

Patched version: 5.0.1

From: ?npm/mocha@8.1.3npm/flat@4.1.0

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/flat@4.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm registry-auth-token is 95.0% likely obfuscated

Confidence: 0.95

Location: Package overview

From: ?npm/@makeomatic/deploy@10.3.0npm/apidoc@0.25.0npm/apidoc-markdown@5.1.6npm/registry-auth-token@4.2.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/registry-auth-token@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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.

1 participant