Skip to content

build(deps): bump debug and express#2214

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/debug-and-express-4.3.4
Closed

build(deps): bump debug and express#2214
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/debug-and-express-4.3.4

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Oct 25, 2022 •
edited
Loading

Bumps debug and express. These dependencies needed to be updated together.
Updates debug from 0.8.1 to 4.3.4

Release notes

Sourced from [debug's releases](https://github.com/debug-js/debug/releases).

4.3.4

What's Changed

New Contributors

Full Changelog: [https://github.com/debug-js/debug/compare/4.3.3...4.3.4](https://github.com/debug-js/debug/compare/4.3.3...4.3.4)

4.3.3

Patch Release 4.3.3

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

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](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](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.

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by [qix](https://www.npmjs.com/~qix), a new releaser for debug since your current version.


Updates express from 3.4.8 to 4.18.1

Release notes

Sourced from [express's releases](https://github.com/expressjs/express/releases).

4.18.1

  • Fix hanging on large stack of sync routes

4.18.0

  • Add "root" option to res.download
  • Allow options without filename in res.download
  • Deprecate string and non-integer arguments to res.status
  • Fix behavior of null/undefined as maxAge in res.cookie
  • Fix handling very large stacks of sync middleware
  • Ignore Object.prototype values in settings through app.set/app.get
  • Invoke default with same arguments as types in res.format
  • Support proper 205 responses using res.send
  • Use http-errors for res.format error
  • deps: body-parser@1.20.0
    • Fix error message for json parse whitespace in strict
    • Fix internal error when inflated body exceeds limit
    • Prevent loss of async hooks context
    • Prevent hanging when request already read
    • deps: depd@2.0.0
    • deps: http-errors@2.0.0
    • deps: on-finished@2.4.1
    • deps: qs@6.10.3
    • deps: raw-body@2.5.1
  • deps: cookie@0.5.0
    • Add priority option
    • Fix expires option to reject invalid dates
  • deps: depd@2.0.0
    • Replace internal eval usage with Function constructor
    • Use instance methods on process to check for listeners
  • deps: finalhandler@1.2.0
    • Remove set content headers that break response
    • deps: on-finished@2.4.1
    • deps: statuses@2.0.1
  • deps: on-finished@2.4.1
    • Prevent loss of async hooks context
  • deps: qs@6.10.3
  • deps: send@0.18.0
    • Fix emitted 416 error missing headers property
    • Limit the headers removed for 304 response
    • deps: depd@2.0.0
    • deps: destroy@1.2.0
    • deps: http-errors@2.0.0
    • deps: on-finished@2.4.1
    • deps: statuses@2.0.1
  • deps: serve-static@1.15.0
    • deps: send@0.18.0
  • deps: statuses@2.0.1
    • Remove code 306
    • Rename 425 Unordered Collection to standard 425 Too Early

... (truncated)

Changelog

Sourced from [express's changelog](https://github.com/expressjs/express/blob/master/History.md).

4.18.1 / 2022-04-29

  • Fix hanging on large stack of sync routes

4.18.0 / 2022-04-25

  • Add "root" option to res.download
  • Allow options without filename in res.download
  • Deprecate string and non-integer arguments to res.status
  • Fix behavior of null/undefined as maxAge in res.cookie
  • Fix handling very large stacks of sync middleware
  • Ignore Object.prototype values in settings through app.set/app.get
  • Invoke default with same arguments as types in res.format
  • Support proper 205 responses using res.send
  • Use http-errors for res.format error
  • deps: body-parser@1.20.0
    • Fix error message for json parse whitespace in strict
    • Fix internal error when inflated body exceeds limit
    • Prevent loss of async hooks context
    • Prevent hanging when request already read
    • deps: depd@2.0.0
    • deps: http-errors@2.0.0
    • deps: on-finished@2.4.1
    • deps: qs@6.10.3
    • deps: raw-body@2.5.1
  • deps: cookie@0.5.0
    • Add priority option
    • Fix expires option to reject invalid dates
  • deps: depd@2.0.0
    • Replace internal eval usage with Function constructor
    • Use instance methods on process to check for listeners
  • deps: finalhandler@1.2.0
    • Remove set content headers that break response
    • deps: on-finished@2.4.1
    • deps: statuses@2.0.1
  • deps: on-finished@2.4.1
    • Prevent loss of async hooks context
  • deps: qs@6.10.3
  • deps: send@0.18.0
    • Fix emitted 416 error missing headers property
    • Limit the headers removed for 304 response
    • deps: depd@2.0.0
    • deps: destroy@1.2.0
    • deps: http-errors@2.0.0
    • deps: on-finished@2.4.1
    • deps: statuses@2.0.1
  • deps: serve-static@1.15.0
    • deps: send@0.18.0

... (truncated)

Commits
  • d854c43 4.18.1
  • b02a95c build: Node.js@16.15
  • 631ada0 Fix hanging on large stack of sync routes
  • 75e0c7a bench: remove unused parameter
  • e2482b7 build: ejs@3.1.7
  • 2df96e3 build: supertest@6.2.3
  • a38fae1 build: mocha@9.2.2
  • 547fdd4 4.18.0
  • 0b330ef bench: print latency and vary connections
  • 158a170 build: support Node.js 18.x
  • Additional commits viewable in [compare view](https://github.com/expressjs/express/compare/3.4.8...4.18.1)
Maintainer changes

This version was pushed to npm by [dougwilson](https://www.npmjs.com/~dougwilson), a new releaser for express since your current version.


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

┆Issue is synchronized with this Asana task by Unito

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Oct 25, 2022
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch from 8a1a37d to 7abfda9 Compare October 25, 2022 12:25
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch from 7abfda9 to ede5562 Compare November 1, 2022 15:24
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch from ede5562 to d86a734 Compare November 9, 2022 13:18
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch 2 times, most recently from 29d23ff to 6de0885 Compare November 18, 2022 09:15
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch 4 times, most recently from 6ceb6a4 to 64bbbe0 Compare November 29, 2022 10:51
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch 3 times, most recently from fa3cf91 to f8c9e91 Compare December 23, 2022 11:56
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch 3 times, most recently from 6da7411 to 7c4c381 Compare January 4, 2023 05:17
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch 2 times, most recently from 050e976 to 775f7de Compare January 10, 2023 08:47
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch from 775f7de to 929b162 Compare January 30, 2023 10:50
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch 2 times, most recently from 1a3b503 to 54313cf Compare February 19, 2023 06:31
@dependabot
build(deps): bump debug and express
a54e088 
Bumps [debug](https://github.com/debug-js/debug) and [express](https://github.com/expressjs/express). These dependencies needed to be updated together.

Updates `debug` from 0.8.1 to 4.3.4
- [Release notes](https://github.com/debug-js/debug/releases)
- [Commits](debug-js/debug@0.8.1...4.3.4)

Updates `express` from 3.4.8 to 4.18.1
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](expressjs/express@3.4.8...4.18.1)

---
updated-dependencies:
- dependency-name: debug
  dependency-type: indirect
- dependency-name: express
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch from 54313cf to a54e088 Compare March 3, 2023 09:47
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Mar 7, 2023

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

@olgahaha olgahaha closed this Nov 12, 2024
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Nov 12, 2024

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/debug-and-express-4.3.4 branch November 12, 2024 09:38
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

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@olgahaha