🚨 [security] [backend] Update mongoose 6.0.8 → 7.6.4 (major) #265
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?
✳️ mongoose (6.0.8 → 7.6.4) · Repo · Changelog
Security Advisories 🚨
🚨 Mongoose Prototype Pollution vulnerability
🚨 Mongoose Prototype Pollution vulnerability
🚨 Prototype pollution Schema.path in automattic/mongoose
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 20 commits:
chore: release 7.6.4
Merge pull request #14017 from Automattic/vkarpov15/gh-13973-2
Merge pull request #14011 from Automattic/vkarpov15/gh-13978
test: modify test name re: code review comments
Update test/schema.test.js
fix(document): handle #9396 case by only applying #13973 logic if in transaction
fix(connection): retain modified status for documents created outside a transaction during transaction retries
fix(schema): handle recursive schemas in discriminator definitions
fix: handle casting $or within $elemMatch
Merge pull request #13998 from suzuki/fix/doc-plungins
Merge pull request #13995 from Freezystem/fix.add-fullpath-to-validator-props
Merge pull request #13996 from Automattic/IslandRhythms/gh13863
Update model.js
fix(document): fix differences between sample codes and documentation
fix(populate): allow using `options: { strictPopulate: false }` to disable strict populate
fix: lint
write test
Add fullPath to ValidatorProps
Merge pull request #13992 from suzuki/fix/doc-typescript-query-helper
fix(document): fix missing import and change wrong variable name
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.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