Skip to content
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

fix(deps): update all non-major dependencies #101

Merged
merged 1 commit into from
Jan 26, 2022
Merged

fix(deps): update all non-major dependencies #101

merged 1 commit into from
Jan 26, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 26, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
debug 4.3.2 -> 4.3.3 age adoption passing confidence
eslint-plugin-import 2.25.2 -> 2.25.4 age adoption passing confidence
jest (source) 27.3.1 -> 27.4.7 age adoption passing confidence
nock 13.1.4 -> 13.2.2 age adoption passing confidence
node 14.18.1 -> 14.18.3 age adoption passing confidence

Release Notes

visionmedia/debug

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.

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.

import-js/eslint-plugin-import

v2.25.4

Compare Source

Fixed
Changed
  • [no-default-import]: report on the token "default" instead of the entire node ([#​2299], thanks [@​pmcelhaney])
  • [Docs] [order]: Remove duplicate mention of default ([#​2280], thanks [@​johnthagen])
  • [Deps] update eslint-module-utils

v2.25.3

Compare Source

Fixed
Changed
facebook/jest

v27.4.7

Compare Source

Fixes
  • jest-config Add missing @babel/core dependency (#​12216)

v27.4.6

Compare Source

Fixes
  • [jest-environment-node] Add AbortSignal (#​12157)
  • [jest-environment-node] Add Missing node global performance (#​12002)
  • [jest-runtime] Handle missing mocked property (#​12213)
  • [@jest/transform] Update dependency package pirates to 4.0.4 (#​12002)
Performance
  • jest-config perf: only register ts-node once when loading TS config files (#​12160)

v27.4.5

Compare Source

Fixes
  • [jest-worker] Stop explicitly passing process.env (#​12141)

v27.4.4

Compare Source

Fixes
  • [babel-jest] Add process.version chunk to the cache key (#​12122)
  • [jest-environment] Add mocked to jest object (#​12133)
  • [jest-worker] Stop explicitly passing execArgv (#​12128)
Chore & Maintenance
  • [website] Fix the card front that looks overlapping part of the card back

v27.4.3

Compare Source

Fixes
  • [jest-environment-jsdom] Remove @types/jsdom dependency (and make its dom property private) (#​12107)

v27.4.2

Compare Source

Fixes
  • [jest-worker] Add additional execArgv to filter (#​12103)

v27.4.1

Compare Source

Fixes
  • [jest-worker] Filter execArgv correctly (#​12097)

v27.4.0

Compare Source

Features
  • [expect] Enhancing the toHaveProperty matcher to support array selection (#​12092)
  • [jest-core] Add support for testResultsProcessor written in ESM (#​12006)
  • [jest-diff, pretty-format] Add compareKeys option for custom sorting of object keys (#​11992)
  • [jest-mock] Add ts-jest mock util functions (#​12089)
Fixes
  • [expect] Allow again expect.Matchers generic with single value (#​11986)
  • [jest-circus, jest-jasmine2] Avoid false concurrent test failures due to unhandled promise rejections (#​11987)
  • [jest-config] Add missing slash dependency to package.json (#​12080)
  • [jest-core] Incorrect detection of open ZLIB handles (#​12022)
  • [jest-diff] Break dependency cycle (#​10818)
  • [jest-environment-jsdom] Add @types/jsdom dependency (#​11999)
  • [jest-environment-jsdom] Do not reset the global.document too early on teardown (#​11871)
  • [jest-transform] Improve error and warning messages (#​11998)
  • [jest-worker] Pass execArgv correctly to worker_threads worker (#​12069)
Chore & Maintenance
  • [docs] CLI options alphabetized (#​11586)
  • [jest-runner] Add info regarding timers to forcedExit message(#​12083)
  • [*] Replaced substr method with substring (#​12066)
  • [*] Add types entry to all export maps (#​12073)
nock/nock

v13.2.2

Compare Source

Bug Fixes
  • allowUnocked not working with regex host + request body match (#​2277) (ac7b4fd)

v13.2.1

Compare Source

Bug Fixes

v13.2.0

Compare Source

Features
nodejs/node

v14.18.3

Compare Source

This is a security release.

Notable changes
Improper handling of URI Subject Alternative Names (Medium)(CVE-2021-44531)

Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.

Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option.

More details will be available at CVE-2021-44531 after publication.

Certificate Verification Bypass via String Injection (Medium)(CVE-2021-44532)

Node.js converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.

Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the --security-revert command-line option.

More details will be available at CVE-2021-44532 after publication.

Incorrect handling of certificate subject and issuer fields (Medium)(CVE-2021-44533)

Node.js did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.

Affected versions of Node.js do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.

More details will be available at CVE-2021-44533 after publication.

Prototype pollution via console.table properties (Low)(CVE-2022-21824)

Due to the formatting logic of the console.table() function it was not safe to allow user controlled input to be passed to the properties parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be __proto__. The prototype pollution has very limited control, in that it only allows an empty string to be assigned numerical keys of the object prototype.

Versions of Node.js with the fix for this use a null protoype for the object these properties are being assigned to.

More details will be available at CVE-2022-21824 after publication.

Thanks to Patrik Oldsberg (rugvip) for reporting this vulnerability.

Commits

v14.18.2

Compare Source

Notable changes

This release contains a c-ares update to fix a regression introduced in
Node.js 14.17.5 resolving CNAME records containing underscores
#​39780.

Also included are commits to allow Node.js 14 to continue to build and
pass tests on our Jenkins CI, including adding Python 3.10 to the list
of allowable Python versions for building.

Commits

Configuration

📅 Schedule: "after 3am and before 10pm" (UTC).

🚦 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, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot added dependencies Updating dependencies minor A minor or patch level change labels Jan 26, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5516664 to 1e6f33e Compare January 26, 2022 17:27
@coveralls
Copy link

Pull Request Test Coverage Report for Build 7b65be29-2ae0-4ea8-84a5-4ddce7dc31b0

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%
Totals Coverage Status
Change from base Build 415e5e94-5c19-4264-8c2c-01695fd92503: 0.0%
Covered Lines: 116
Relevant Lines: 116
💛 - Coveralls

@bnormington bnormington merged commit 33dd0c1 into main Jan 26, 2022
@bnormington bnormington deleted the renovate/all-minor-patch branch January 26, 2022 18:50
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 Updating dependencies minor A minor or patch level change
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@coveralls @bnormington @renovate-bot