🚨 [security] [backend] Update mongoose 6.0.8 → 7.4.1 (major) #238
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.4.1) · 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 23 commits:
chore: release 7.4.1Merge pull request #13644 from Automattic/vkarpov15/gh-13609fix(document): clean up all nested subdocs modified state on savefix: avoid applying defaults when casting for $pull() re: #13609Merge pull request #13636 from omran95/omran95/add-inline-comment-to-runValidators-query-typesMerge pull request #13638 from Automattic/IslandRhythms/gh-13501Update document.jsfix doc.validate docMerge pull request #13612 from Automattic/IslandRhythms/gh-13592Update applyWriteConcern.test.jsMerge pull request #13628 from Automattic/vkarpov15/fix-ts-map-schema-typeMerge pull request #13632 from Automattic/vkarpov15/gh-13601Merge pull request #13634 from Automattic/vkarpov15/gh-13599Update test/document.test.jsUpdate test/document.test.jsMerge pull request #13635 from Automattic/vkarpov15/gh-13616Add inline comment to mainly tell the default value of the runValidator option in the QueryOptions interfaceUpdate docs/middleware.mddocs: fix some more examples that still use callbacks re: #13616docs: rework several code examples that still use callbacksfix(schema): avoid propagating `toObject.transform` and `toJSON.transform` option to implicitly created schemastypes: correctly handle `pre('deleteOne', { document: true })`types(schema): handle `type: Schema.Types.Map` in TypeScript👉 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