eddieren.me icon indicating copy to clipboard operation
eddieren.me copied to clipboard

Published 20 hours ago • verified publisher icon EdwaRen

Bump debug, compression, express and serve-index

Open dependabot[bot] opened this issue 2 years ago • 0 comments

Bumps debug, compression, express and serve-index. These dependencies needed to be updated together. Updates debug from 2.6.8 to 4.3.4

Release notes

Sourced from debug's releases.

4.3.4

What's Changed

New Contributors

Full Changelog: 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, 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.

... (truncated)

Commits
  • da66c86 4.3.4
  • 9b33412 replace deprecated String.prototype.substr() (#876)
  • c0805cc add section about configuring JS console to show debug messages (#866)
  • 043d3cd 4.3.3
  • 4079aae update license and more maintainership information
  • 19b36c0 update repository location + maintainership information
  • f851b00 adds README section regarding usage in child procs (#850)
  • d177f2b Remove accidental epizeuxis
  • e47f96d 4.3.2
  • 1e9d38c cache enabled status per-logger (#799)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by qix, a new releaser for debug since your current version.


Updates compression from 1.7.0 to 1.7.4

Release notes

Sourced from compression's releases.

1.7.4

  • deps: compressible@~2.0.16
    • Mark text/less as compressible
    • deps: mime-db@'>= 1.38.0 < 2'
  • deps: on-headers@~1.0.2
    • Fix res.writeHead patch missing return value
  • perf: prevent unnecessary buffer copy

1.7.3

  • deps: accepts@~1.3.5
    • deps: mime-types@~2.1.18
  • deps: compressible@~2.0.14
    • Mark all XML-derived types as compressible
    • deps: mime-db@'>= 1.34.0 < 2'
  • deps: [email protected]

1.7.2

  • deps: compressible@~2.0.13
    • deps: mime-db@'>= 1.33.0 < 2'

1.7.1

  • deps: accepts@~1.3.4
    • deps: mime-types@~2.1.16
  • deps: [email protected]
  • deps: compressible@~2.0.11
    • deps: mime-db@'>= 1.29.0 < 2'
  • deps: [email protected]
  • deps: vary@~1.1.2
    • perf: improve header token parsing speed
Changelog

Sourced from compression's changelog.

1.7.4 / 2019-03-18

  • deps: compressible@~2.0.16
    • Mark text/less as compressible
    • deps: mime-db@'>= 1.38.0 < 2'
  • deps: on-headers@~1.0.2
    • Fix res.writeHead patch missing return value
  • perf: prevent unnecessary buffer copy

1.7.3 / 2018-07-15

  • deps: accepts@~1.3.5
    • deps: mime-types@~2.1.18
  • deps: compressible@~2.0.14
    • Mark all XML-derived types as compressible
    • deps: mime-db@'>= 1.34.0 < 2'
  • deps: [email protected]

1.7.2 / 2018-02-18

  • deps: compressible@~2.0.13
    • deps: mime-db@'>= 1.33.0 < 2'

1.7.1 / 2017-09-26

  • deps: accepts@~1.3.4
    • deps: mime-types@~2.1.16
  • deps: [email protected]
  • deps: compressible@~2.0.11
    • deps: mime-db@'>= 1.29.0 < 2'
  • deps: [email protected]
  • deps: vary@~1.1.2
    • perf: improve header token parsing speed
Commits

Updates express from 4.15.4 to 4.18.2

Release notes

Sourced from express's releases.

4.18.2

4.18.1

  • Fix hanging on large stack of sync routes

4.18.0

... (truncated)

Changelog

Sourced from express's changelog.

4.18.2 / 2022-10-08

4.18.1 / 2022-04-29

  • Fix hanging on large stack of sync routes

4.18.0 / 2022-04-25

... (truncated)

Commits

Updates serve-index from 1.9.0 to 1.9.1

Release notes

Sourced from serve-index's releases.

1.9.1

  • deps: accepts@~1.3.4
    • deps: mime-types@~2.1.16
  • deps: [email protected]
  • deps: http-errors@~1.6.2
  • deps: mime-types@~2.1.17
    • Add new mime types
    • deps: mime-db@~1.30.0
  • deps: parseurl@~1.3.2
    • perf: reduce overhead for full URLs
    • perf: unroll the "fast-path" RegExp
Changelog

Sourced from serve-index's changelog.

1.9.1 / 2017-09-28

  • deps: accepts@~1.3.4
    • deps: mime-types@~2.1.16
  • deps: [email protected]
  • deps: http-errors@~1.6.2
  • deps: mime-types@~2.1.17
    • Add new mime types
    • deps: mime-db@~1.30.0
  • deps: parseurl@~1.3.2
    • perf: reduce overhead for full URLs
    • perf: unroll the "fast-path" RegExp
Commits

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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependabot[bot] avatar Jan 11 '23 15:01 dependabot[bot]