🚨 [security] [backend] Update mongoose 6.0.8 → 7.3.2 (major) #232
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.3.2) · 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 61 commits:
chore: release 7.3.2Merge pull request #13579 from Automattic/vkarpov15/gh-13531Merge pull request #13581 from hasezoey/updateDevchore(dev-deps): bump mkdirp from 2.1.3 to 3.0.1chore(dev-deps): bump @typescript-eslint/* from 5.60.1 to 5.61.0Merge pull request #13571 from Automattic/vkarpov15/gh-13570fix(model): avoid TypeError if insertMany() fails with error that does not have `writeErrors` propertyUpdate test/query.test.jsMerge branch 'master' into vkarpov15/gh-13570test: add suggested test for missing `op`Merge pull request #13572 from Automattic/vkarpov15/gh-13550Merge pull request #13574 from orgads/merge-typeMerge pull request #13576 from Automattic/vkarpov15/gh-13537docs(connections): clarify that socketTimeoutMS now defaults to 0Types: Reuse MergeType in DiscriminatorSchemafix(query): convert findOneAndUpdate to findOneAndReplace when overwrite set for backwards compat with Mongoose 6fix(query): throw readable error when executing a Query instance without an associated modelMerge pull request #13568 from Automattic/vkarpov15/gh-13548Update docs/migrating_to_7.mddocs(migrating_to_7): add mapReduce() removal to migration guideMerge pull request #13564 from Automattic/dependabot/npm_and_yarn/master/mongodb-memory-server-8.13.0Merge pull request #13563 from Automattic/dependabot/npm_and_yarn/master/babel/preset-env-7.22.5chore(deps-dev): bump @babel/preset-env from 7.22.4 to 7.22.5Merge pull request #13566 from Automattic/dependabot/npm_and_yarn/master/typescript-5.1.6Merge pull request #13565 from Automattic/dependabot/npm_and_yarn/master/eslint-8.44.0Merge pull request #13561 from Automattic/dependabot/npm_and_yarn/master/typescript-eslint/eslint-plugin-5.60.1Merge pull request #13562 from Automattic/dependabot/npm_and_yarn/master/dotenv-16.3.1chore(deps-dev): bump typescript from 5.1.3 to 5.1.6chore(deps-dev): bump @typescript-eslint/eslint-pluginchore(deps-dev): bump eslint from 8.41.0 to 8.44.0Merge pull request #13560 from Automattic/dependabot/npm_and_yarn/master/typescript-eslint/parser-5.60.1Merge pull request #13559 from Automattic/dependabot/npm_and_yarn/master/babel/core-7.22.5Merge pull request #13557 from Automattic/dependabot/npm_and_yarn/master/sinon-15.2.0Merge pull request #13556 from Automattic/dependabot/npm_and_yarn/master/webpack-5.88.1Merge pull request #13555 from Automattic/dependabot/github_actions/master/actions/checkout-3.5.3chore(deps-dev): bump mongodb-memory-server from 8.12.2 to 8.13.0chore(deps-dev): bump dotenv from 16.1.3 to 16.3.1chore(deps-dev): bump @typescript-eslint/parser from 5.59.8 to 5.60.1chore(deps-dev): bump @babel/core from 7.22.1 to 7.22.5chore(deps-dev): bump sinon from 15.1.0 to 15.2.0chore(deps-dev): bump webpack from 5.85.0 to 5.88.1chore(deps): bump actions/checkout from 3.5.2 to 3.5.3Merge pull request #13551 from hasezoey/routineMDfixMerge pull request #13552 from hasezoey/addMarkdownLintchore(workflows/documentation): lint MD files with "markdownlint-cli2"docs(middleware): remove "new in 4.5.0" messagedocs: fix header skipping header levelsdocs(deprecations): change links to be validdocs: change all non-excluded files to have a h1 headingdocs: add language to missing code-blocksdocs: apply automatically fixable ruleschore: add "markdownlint-cli2"chore(eslintrc): also lint all "." filesdocs: routine lint for markdown code runMerge pull request #13543 from Automattic/vkarpov15/gh-13534types: support `mongoose.Schema.ObjectId` as alias for `mongoose.Schema.Types.ObjectId`Merge pull request #13541 from Automattic/vkarpov15/remove-internal-callbackstest: try cleaning up data to fix deno testsMerge pull request #13540 from Metehan-Altuntekin/patch-1refactor: avoid using callbacks for internal `deleteOne()` and `find()` callsdocs(schemas): fix typo in schemas.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