🚨 [security] Update joi 17.6.0 → 18.2.1 (major) - #28
Open
depfu[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚨 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?
✳️ joi (17.6.0 → 18.2.1) · Repo · Changelog
Security Advisories 🚨
🚨 joi has an uncaught RangeError on deeply nested input through recursive `link()` schemas
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
11.0.4
11.0.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 25 commits:
11.0.7Fix cloning Util.inherit() subclassed errors. Backports #40111.0.6Fix Error clone() when structuredClone uses bad prototype11.0.5fix: missing stack starting from node 21+chore: pin eslint-pluginFix default values for `merge.Options` interface11.0.4fix: provide reference to TS types for export map (#389)11.0.3Support the URL type (#392)11.0.2chore: add individual module types11.0.1Explicitly export methods11.0.0Refactor AssertError (#382)10.0.1Updates assert() type to declare condition to be true (#383)Fix version range (#379)Fix license years for Sideway versus contributors (#378)10.0.0Remove CI reference to v10 branchMerge remote-tracking branch 'origin/v10'Commits
See the full diff on Github. The new version differs by 10 commits:
6.0.2chore: use standard require instead of exports (#71)6.0.1chore: bump hoek (#70)6.0.0Remove CI reference to v6 branchSupport node v18 and drop node v12 (#69)Add @types/node to dev depsadd dispatcher and use shared configadd IDE linting🆕 @​hapi/address (added, 5.1.1)
🆕 @​hapi/formula (added, 3.0.2)
🆕 @​hapi/pinpoint (added, 2.0.1)
🆕 @​hapi/tlds (added, 1.1.7)
🆕 @​standard-schema/spec (added, 1.1.0)
🗑️ @​sideway/address (removed)
🗑️ @​sideway/formula (removed)
🗑️ @​sideway/pinpoint (removed)
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