fix(deps): update npm dependencies updates #116

renovate · 2025-11-03T02:28:06Z

This PR contains the following updates:

Package	Change	Age	Confidence
cookie-parser	`1.4.5` -> `1.4.7`
cypress (source)	`15.5.` -> `15.6.`
debug	`4.3.1` -> `4.4.3`
http-errors	`1.8.0` -> `1.8.1`
morgan	`1.10.0` -> `1.10.1`
nodemon (source)	`2.0.7` -> `2.0.22`
release-it	`19.0.5` -> `19.0.6`

Release Notes

expressjs/cookie-parser (cookie-parser)

`v1.4.7`

Compare Source

==========

deps: cookie@0.7.2
- Fix object assignment of hasOwnProperty
deps: cookie@0.7.1
- Allow leading dot for domain
  - Although not permitted in the spec, some users expect this to work and user agents ignore the leading dot according to spec
- Add fast path for serialize without options, use obj.hasOwnProperty when parsing
deps: cookie@0.7.0
- perf: parse cookies ~10% faster
- fix: narrow the validation of cookies to match RFC6265
- fix: add main to package.json for rspack
deps: cookie@0.6.0
- Add partitioned option
deps: cookie@0.5.0
- Add priority option
- Fix expires option to reject invalid dates
- pref: improve default decode speed
- pref: remove slow string split in parse
deps: cookie@0.4.2
- pref: read value only when assigning in parse
- pref: remove unnecessary regexp in parse

`v1.4.6`

Compare Source

==================

deps: cookie@0.4.1

cypress-io/cypress (cypress)

`v15.6.0`

Compare Source

Changelog: https://docs.cypress.io/app/references/changelog#15-6-0

debug-js/debug (debug)

`v4.4.3`

Compare Source

Functionally identical release to 4.4.1.

Version 4.4.2 is compromised. Please see #1005.

`v4.4.1`

Compare Source

What's Changed

fix(Issue-996): replace whitespaces in namespaces string with commas globally by @pdahal-cx in #997
fixes #987 fallback to localStorage.DEBUG if debug is not defined by @lzilioli in #988

New Contributors

@pdahal-cx made their first contribution in #997
@lzilioli made their first contribution in #988

Full Changelog: debug-js/debug@4.4.0...4.4.1

`v4.4.0`

Compare Source

Fixes (hopefully) the inefficient regex warnings in .enable().

Minor version as this is invariably going to break certain users who misuse the .enable() API and expected it to work with regexes, which was never supported nor documented. That's on you, sorry - that functionality won't be added back.

Full Changelog: debug-js/debug@4.3.7...4.4.0

`v4.3.7`

Compare Source

What's Changed

Upgrade ms to version 2.1.3 by @realityking in #819

Full Changelog: debug-js/debug@4.3.6...4.3.7

`v4.3.6`

Compare Source

What's Changed

Avoid using deprecated RegExp.$1 by @bluwy in #969

New Contributors

@bluwy made their first contribution in #969

Full Changelog: debug-js/debug@4.3.5...4.3.6

`v4.3.5`

Compare Source

Patch

cac39b1 Fix/debug depth (#926)

Thank you @calvintwr for the fix.

`v4.3.4`

Compare Source

What's Changed

Add section about configuring JS console to show debug messages by @gitname in #866
Replace deprecated String.prototype.substr() by @CommanderRoot in #876

New Contributors

@gitname made their first contribution in #866
@CommanderRoot made their first contribution in #876

Full Changelog: debug-js/debug@4.3.3...4.3.4

`v4.3.3`

Compare Source

Patch Release 4.3.3

This is a documentation-only release. Further, the repository was transferred. Please see notes below.

Migrates repository from https://github.com/visionmedia/debug to https://github.com/debug-js/debug. Please see notes below as to why this change was made.
Updates repository maintainership information
Updates the copyright (no license terms change has been made)
Removes accidental epizeuxis (#828)
Adds README section regarding usage in child procs (#850)

Thank you to @taylor1791 and @kristofkalocsai for their contributions.

Repository Migration Information

I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.

Q: What impact will this have on me?

In most cases, you shouldn't notice any change.

The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a "debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.

Q: What are the security implications of this change?

If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.

Even in such a case, however, the officially released package on npm (debug) would not be affected. That package is still very much under control (even more than it used to be).

Q: What should I do if I encounter an issue related to the migration?

Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.

Q: Why was this done as a 'patch' release? Isn't this breaking?

No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.

Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.

I understand there are a lot of edge cases so please open issues as needed so I can assist in any way necessary.

Q: Why was the repository transferred?

I'll just list them off in no particular order.

The old organization was defunct and abandoned.
I was not an owner of the old organization and thus could not ban the non-trivial amount of spam users or the few truly abusive users from the org. This hindered my ability to properly maintain this package.
The debug ecosystem intends to grow beyond a single package, and since new packages could not be created in the old org (nor did it make sense for them to live there), a new org made the most sense - especially from a security point of view.
The old org has way, way too many approved members with push access, for which there was nothing I could do. This presented a pretty sizable security risk given that many packages in recent years have fallen victim to backdoors and the like due to lax security access.

Q: Was this approved?

Yes.^[archive]

Q: Do I need to worry about another migration sometime in the future?

No.

`v4.3.2`

Compare Source

Patch release 4.3.2

Caches enabled statuses on a per-logger basis to speed up .enabled checks (#799)

Thank you @omg!

jshttp/http-errors (http-errors)

`v1.8.1`

Compare Source

==================

deps: toidentifier@1.0.1

expressjs/morgan (morgan)

`v1.10.1`

Compare Source

===================

deps: on-headers@~1.1.0
- Fix CVE-2025-7339 (GHSA-76c9-3jph-rj3q)

add support for SIGINT on Windows (fixes issue #1720) (#1853) (500c1b0)

release-it/release-it (release-it)

`v19.0.6`

Compare Source

Update list of projects using release-it (92b49d3)
Bump github/codeql-action from 2 to 4 (#1253) (21309d3) - thanks @dependabot[bot]!
Bump actions/setup-node from 5 to 6 (#1255) (3fbaab1) - thanks @dependabot[bot]!
Test in node 24 (7a12b12)
Upgrade c12 (resolve #1254) (1f48d03)

Configuration

📅 Schedule: Branch creation - "before 8am on monday" in timezone Europe/Paris, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

renovate bot force-pushed the renovate/npm-dependencies-updates branch from 4fae6a0 to e13033e Compare November 4, 2025 23:30

fix(deps): update npm dependencies updates

627e8cb

renovate bot force-pushed the renovate/npm-dependencies-updates branch from e13033e to 627e8cb Compare November 5, 2025 18:33

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update npm dependencies updates #116

fix(deps): update npm dependencies updates #116

Uh oh!

renovate bot commented Nov 3, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

fix(deps): update npm dependencies updates #116

Are you sure you want to change the base?

fix(deps): update npm dependencies updates #116

Uh oh!

Conversation

renovate bot commented Nov 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

Patch

What's Changed

New Contributors

Patch Release 4.3.3

Repository Migration Information

Q: What impact will this have on me?

Q: What are the security implications of this change?

Q: What should I do if I encounter an issue related to the migration?

Q: Why was this done as a 'patch' release? Isn't this breaking?

Q: Why was the repository transferred?

Q: Was this approved?

Q: Do I need to worry about another migration sometime in the future?

Patch release 4.3.2

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Nov 3, 2025 •

edited

Loading