🚨 [security] [backend] Update mongoose 6.0.8 → 8.0.2 (major)#272
Closed
depfu[bot] wants to merge 1 commit intomainfrom
Closed
🚨 [security] [backend] Update mongoose 6.0.8 → 8.0.2 (major)#272depfu[bot] wants to merge 1 commit intomainfrom
depfu[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
|
Closed in favor of #275. |
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.2) · 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 70 commits:
chore: release 8.0.2Merge branch '7.x'Merge pull request #14125 from hasezoey/fixWebsiteMongooseMerge pull request #14126 from hasezoey/80releaseMerge pull request #14116 from hasezoey/slightWebsitechore: release 7.6.6Merge pull request #14102 from Automattic/IslandRhythms/cleanuptypes: make property names show up in intellisense for UpdateQuerychore: correctly clean relative to version pathUpdate package.jsonUpdate package.jsonUpdate scripts/website.jsdocs(README): update breaking change versionMerge pull request #14120 from Automattic/vkarpov15/gh-11380docs(source/api): fix "index.js" -> "mongoose.js" renameMerge pull request #14123 from Automattic/vkarpov15/gh-14090chore(scripts/website): change "getTests" to be syncchore: add extra check to prevent copying non-versioned deploy to tmp, handle ENOENT error, consistently check for truthy DOCS_DEPLOYMerge branch '7.x' into IslandRhythms/cleanuptypes: make property names show up in intellisense for UpdateQueryMerge pull request #14118 from Automattic/vkarpov15/gh-14077perf: avoid double-calling setters when pushing onto an arrayperf: avoid mutating internal state if setting state to current re: #11380perf: one more quick improvementperf: correct way to avoid calling concat() re: #11380perf(array): use push() instead of concat() for $push atomics re: #11380fix(populate): set populated docs in correct order when populating virtual underneath doc array with justOne (#14105)fix(populate): set populated docs in correct order when populating virtual underneath doc array with justOne (#14105)types(query): base filters and projections off of RawDocType instead of DocType so autocomplete doesn't show populatechore(scripts/website): add some missing ";"chore(scripts/website): convert a comment to JSDOCchore(scripts/website): refactor acquit file loadingstyle(scripts/website): directly call "markdown.use"Merge pull request #14112 from Automattic/vkarpov15/gh-14072refactor: address code review commentsMerge branch '7.x' into IslandRhythms/cleanupMerge pull request #14099 from csy1204/fix/gh-14098Merge pull request #14110 from Automattic/vkarpov15/gh-14081types(models): add missing per bulk write optionstypes(models): allow specifying `timestamps` as inline option for bulkWrite() operationstypes(document): correct return type for `doc.deleteOne()` re: Mongoose 8 breaking changeMerge pull request #14088 from Automattic/vkarpov15/gh-14003Merge pull request #14095 from Automattic/vkarpov15/gh-13424chore: move cleanup logic from npm scripts to website.js scriptMerge branch '7.x' into IslandRhythms/cleanuptypes: quick fix to handle empty objectsMerge branch 'master' into vkarpov15/gh-13424Merge pull request #14096 from Automattic/vkarpov15/gh-13970refactor: quick cleanup to avoid building curPath when not necessary with #14099Merge pull request #14099 from csy1204/fix/gh-14098Merge pull request #14086 from laupow/patch-1Merge pull request #14084 from lorand-horvath/patch-13Fix test errorFix lint errorRemove console.logAdd test for gh-14098Update curPath for nested pathfix: upgrade mongodb -> 5.9.1 to fix #13829test(query): remove unnecessary query test codetypes: allow defining document array using `[{ prop: String }]` syntaxinitial draftdocs: remove "DEPRECATED" warning mistakenly added to `read()` tags paramtypes: fix issues backporting #14078 to 7.xFix: Mongoose types incorrect for when includeResultMetadata: true is set (#14078)Fix: Mongoose types incorrect for when includeResultMetadata: true is set (#14078)test: add test for #14003types(model): support calling `Model.validate()` with `pathsToSkip` optiondocs: consistent spacingdocs: fix rendering of 7.x compatibilityBump mongodb driver to 5.9.1👉 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