Skip to content

🚨 [security] [backend] Update nodemon 2.0.13 → 3.1.1 (major) #326

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.

Sign up for GitHub

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

Jump to bottom
Closed
depfu wants to merge 1 commit into from
Closed

🚨 [security] [backend] Update nodemon 2.0.13 → 3.1.1 (major) #326

depfu wants to merge 1 commit into from

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented May 26, 2024

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ nodemon (2.0.13 → 3.1.1) · Repo

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ anymatch (indirect, 3.1.2 → 3.1.3) · Repo

Release Notes

3.1.3

Fixes:

  • Keep trailing slash on paths
  • Add TypeScript overload for test string being null

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 5 commits:

↗️ binary-extensions (indirect, 2.2.0 → 2.3.0) · Repo

Release Notes

2.3.0

v2.2.0...v2.3.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ braces (indirect, 3.0.2 → 3.0.3) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 12 commits:

↗️ chokidar (indirect, 3.5.2 → 3.6.0) · Repo · Changelog

Release Notes

3.6.0

What's Changed

New Contributors

Full Changelog: 3.5.3...3.6.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 38 commits:

↗️ fill-range (indirect, 7.0.1 → 7.1.1) · Repo

Commits

See the full diff on Github. The new version differs by 7 commits:

↗️ fsevents (indirect, 2.3.2 → 2.3.3) · Repo

Release Notes

2.3.3

Released to npm as v2.3.3

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 7 commits:

↗️ is-glob (indirect, 4.0.2 → 4.0.3) · Repo

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ minimatch (indirect, 3.0.4 → 3.1.2) · Repo · Changelog

Security Advisories 🚨

🚨 minimatch ReDoS vulnerability

A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.

Commits

See the full diff on Github. The new version differs by 17 commits:

↗️ picomatch (indirect, 2.3.0 → 2.3.1) · Repo · Changelog

Release Notes

2.3.1

Fixed

  • Fixes bug when a pattern containing an expression after the closing parenthesis (/!(*.d).{ts,tsx}) was incorrectly converted to regexp (9f241ef).

Changed

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 13 commits:

↗️ semver (indirect, 5.7.1 → 7.6.2) · Repo · Changelog

Security Advisories 🚨

🚨 semver vulnerable to Regular Expression Denial of Service

Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.

🚨 semver vulnerable to Regular Expression Denial of Service

Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.

🚨 semver vulnerable to Regular Expression Denial of Service

Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ touch (indirect, 3.1.0 → 3.1.1) · Repo

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ undefsafe (indirect, 2.0.3 → 2.0.5) · Repo

Commits

See the full diff on Github. The new version differs by 2 commits:

🆕 simple-update-notifier (added, 2.0.0)

🗑️ @​sindresorhus/is (removed)

🗑️ @​szmarczak/http-timer (removed)

🗑️ abbrev (removed)

🗑️ ansi-align (removed)

🗑️ ansi-regex (removed)

🗑️ ansi-styles (removed)

🗑️ boxen (removed)

🗑️ cacheable-request (removed)

🗑️ camelcase (removed)

🗑️ chalk (removed)

🗑️ ci-info (removed)

🗑️ cli-boxes (removed)

🗑️ clone-response (removed)

🗑️ color-convert (removed)

🗑️ color-name (removed)

🗑️ configstore (removed)

🗑️ crypto-random-string (removed)

🗑️ decompress-response (removed)

🗑️ deep-extend (removed)

🗑️ defer-to-connect (removed)

🗑️ dot-prop (removed)

🗑️ duplexer3 (removed)

🗑️ emoji-regex (removed)

🗑️ end-of-stream (removed)

🗑️ escape-goat (removed)

🗑️ get-stream (removed)

🗑️ global-dirs (removed)

🗑️ got (removed)

🗑️ graceful-fs (removed)

🗑️ has-yarn (removed)

🗑️ http-cache-semantics (removed)

🗑️ import-lazy (removed)

🗑️ imurmurhash (removed)

🗑️ ini (removed)

🗑️ is-ci (removed)

🗑️ is-fullwidth-code-point (removed)

🗑️ is-installed-globally (removed)

🗑️ is-npm (removed)

🗑️ is-obj (removed)

🗑️ is-path-inside (removed)

🗑️ is-typedarray (removed)

🗑️ is-yarn-global (removed)

🗑️ json-buffer (removed)

🗑️ keyv (removed)

🗑️ latest-version (removed)

🗑️ lowercase-keys (removed)

🗑️ lru-cache (removed)

🗑️ make-dir (removed)

🗑️ mimic-response (removed)

🗑️ nopt (removed)

🗑️ normalize-url (removed)

🗑️ once (removed)

🗑️ p-cancelable (removed)

🗑️ package-json (removed)

🗑️ prepend-http (removed)

🗑️ pump (removed)

🗑️ pupa (removed)

🗑️ rc (removed)

🗑️ registry-auth-token (removed)

🗑️ registry-url (removed)

🗑️ responselike (removed)

🗑️ semver-diff (removed)

🗑️ signal-exit (removed)

🗑️ string-width (removed)

🗑️ strip-ansi (removed)

🗑️ strip-json-comments (removed)

🗑️ to-readable-stream (removed)

🗑️ type-fest (removed)

🗑️ typedarray-to-buffer (removed)

🗑️ unique-string (removed)

🗑️ update-notifier (removed)

🗑️ url-parse-lax (removed)

🗑️ widest-line (removed)

🗑️ wrap-ansi (removed)

🗑️ wrappy (removed)

🗑️ write-file-atomic (removed)

🗑️ xdg-basedir (removed)

🗑️ yallist (removed)

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label May 26, 2024
@depfu depfu bot mentioned this pull request May 26, 2024
Closed
@depfu
Copy link
Contributor Author

depfu bot commented May 30, 2024

Closed in favor of #327.

@depfu depfu bot closed this May 30, 2024
@depfu depfu bot deleted the depfu/update/backend/npm/nodemon-3.1.1 branch May 30, 2024 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant