🚨 [security] [backend] Update mongoose 6.0.8 → 7.2.3 (major) #228
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?
✳️ mongoose (6.0.8 → 7.2.3) · Repo · Changelog
Security Advisories 🚨
🚨 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 43 commits:
chore: release 7.2.3Merge pull request #13494 from Automattic/vkarpov15/gh-13482Merge pull request #13493 from Automattic/vkarpov15/gh-13487types: remove generic param that's causing issues for typegoosefix(model): ignore falsy last argument to create() for backwards compatibilityMerge branch '6.x'chore: release 6.11.2chore: use deno v1.34 in test for MMS HTTP issuesMerge pull request #13474 from Automattic/vkarpov15/gh-13400Merge pull request #13470 from Automattic/vkarpov15/gh-13060Merge pull request #13475 from Automattic/vkarpov15/destroy-docsMerge pull request #13476 from Automattic/vkarpov15/gh-13453Merge pull request #13480 from hasezoey/fixPopulateMerge pull request #13481 from hasezoey/updateDenochore(workflows/test): update deno version to 1.34docs(populate): fix accidental removal of textfix(cursor): allow find middleware to modify query cursor optionsdocs(connection): clarify how `Connection.prototype.destroy()` is different from `close()`docs(populate): add a little more info on why we recommend using ObjectId for `_id`Merge pull request #13461 from Automattic/vkarpov15/gh-13449-2types(aggregate): allow object syntax for `$mergeObjects`Merge pull request #13460 from Automattic/dependabot/npm_and_yarn/master/babel/core-7.22.1Merge pull request #13459 from Automattic/dependabot/npm_and_yarn/master/typescript-eslint/eslint-plugin-5.59.8Merge pull request #13463 from Automattic/dependabot/npm_and_yarn/master/webpack-5.85.0Merge pull request #13466 from Automattic/dependabot/npm_and_yarn/master/typescript-5.1.3chore(deps-dev): bump @babel/core from 7.21.8 to 7.22.1chore(deps-dev): bump @typescript-eslint/eslint-pluginchore(deps-dev): bump typescript from 5.0.4 to 5.1.3Merge pull request #13457 from Automattic/dependabot/npm_and_yarn/master/eslint-8.41.0chore(deps-dev): bump eslint from 8.39.0 to 8.41.0Merge pull request #13458 from Automattic/dependabot/npm_and_yarn/master/dotenv-16.1.3Merge pull request #13464 from Automattic/dependabot/npm_and_yarn/master/typescript-eslint/parser-5.59.8Merge pull request #13462 from Automattic/dependabot/npm_and_yarn/master/babel/preset-env-7.22.4Merge pull request #13468 from Automattic/dependabot/npm_and_yarn/master/sinon-15.1.0chore(deps-dev): bump sinon from 15.0.4 to 15.1.0Merge pull request #13452 from alexbevi/alexbevi-patch-1docs: couple style fixeschore(deps-dev): bump @typescript-eslint/parser from 5.59.2 to 5.59.8chore(deps-dev): bump webpack from 5.81.0 to 5.85.0chore(deps-dev): bump @babel/preset-env from 7.21.5 to 7.22.4docs(connections): remove unnecessary mongoose.connect() callchore(deps-dev): bump dotenv from 16.0.3 to 16.1.3Update ssl.md👉 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