🚨 [security] [backend] Update mongoose 6.0.8 → 8.0.3 (major)#275
Closed
depfu[bot] wants to merge 1 commit intomainfrom
Closed
🚨 [security] [backend] Update mongoose 6.0.8 → 8.0.3 (major)#275depfu[bot] wants to merge 1 commit intomainfrom
depfu[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
|
Closed in favor of #285. |
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 → 8.0.3) · 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 58 commits:
chore: release 8.0.3Merge pull request #14160 from Automattic/vkarpov15/gh-14147Merge pull request #14159 from jaypea/patch-1seperate overridesremove whitespacetypes: handle using BigInt global class in schema definitionsadd missing Type for applyDefaultsMerge branch '7.x'chore: release 7.6.7Merge pull request #14156 from hasezoey/removeUtilsOptionsMerge pull request #14155 from Automattic/vkarpov15/gh-3230Merge pull request #14153 from Automattic/vkarpov15/gh-14130Merge branch 'master' into vkarpov15/gh-14130Merge pull request #14152 from Automattic/vkarpov15/gh-13999Merge pull request #14151 from Automattic/vkarpov15/gh-14058refactor(document): remove "clone" where previously necessary because of "utils.options"refactor(utils): remove "options" functionfix(populate): allow deselecting discriminator key when populatingtypes: make findOneAndDelete() without options return result doc, not ModifyResulttypes(model): add no-generic override for `insertMany()` with optionsfix: avoid minimizing single nested subdocs if they are requiredMerge pull request #14150 from Automattic/vkarpov15/gh-13879Update docs/connections.mdUpdate docs/connections.mddocs(connections): add example of registering connection event handlersMerge pull request #14135 from Automattic/vkarpov15/gh-14073Merge pull request #14136 from Automattic/vkarpov15/gh-14132Merge pull request #14143 from Automattic/dependabot/npm_and_yarn/master/markdownlint-cli2-0.11.0chore: fix markdown lintMerge pull request #14146 from Automattic/dependabot/npm_and_yarn/master/typescript-5.3.2Merge pull request #14145 from Automattic/dependabot/npm_and_yarn/master/babel/preset-env-7.23.5chore(deps-dev): bump @babel/preset-env from 7.22.20 to 7.23.5chore(deps-dev): bump typescript from 5.2.2 to 5.3.2Merge pull request #14142 from Automattic/dependabot/npm_and_yarn/master/fs-extra-11.2.0Merge pull request #14141 from Automattic/dependabot/npm_and_yarn/master/eslint-8.55.0Merge pull request #14139 from Automattic/dependabot/npm_and_yarn/master/babel/core-7.23.5chore(deps-dev): bump markdownlint-cli2 from 0.10.0 to 0.11.0chore(deps-dev): bump fs-extra from 11.1.1 to 11.2.0chore(deps-dev): bump eslint from 8.52.0 to 8.55.0chore(deps-dev): bump @babel/core from 7.23.2 to 7.23.5types: add back mistakenly removed findByIdAndRemove() function signaturefix(populate): make sure to call `transform` with the correct index, even if no document foundfix(populate): call `transform` object with single id instead of array when populating a justOne path under an arrayfix(schema): avoid creating unnecessary clone of schematype in nested array so nested document arrays use correct constructorMerge pull request #14128 from Automattic/vkarpov15/gh-14101Merge pull request #14131 from Automattic/vkarpov15/gh-14109test: remove unnecessary code in tests for #14109Merge pull request #14133 from Automattic/IslandRhythms/ref-function-docsUpdate populate.mdUpdate populate.mdUpdate populate.mdchange from arrow function to function declarationUpdate populate.mddocs: link to MongoDB Node driver 6.0 GitHub release rather than changelog entry in migration guidedocs: update version support now that Mongoose 6 is past its legacy support datefix: apply embedded discriminators recursively so fix for #14109 works on discriminators underneath subdocsfix: allow adding discriminators using `Schema.prototype.discriminator()` to subdocuments after defining parent schemafix(schema): avoid creating unnecessary clone of schematype in nested array so nested document arrays use correct constructor👉 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