🚨 [security] [backend] Update mongoose 6.0.8 → 8.0.1 (major)#271
Closed
depfu[bot] wants to merge 1 commit intomainfrom
Closed
🚨 [security] [backend] Update mongoose 6.0.8 → 8.0.1 (major)#271depfu[bot] wants to merge 1 commit intomainfrom
depfu[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
|
Closed in favor of #272. |
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.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 75 commits:
chore: release 8.0.1docs: add mongoose 8 to mongodb server compatibility guideMerge branch '7.x'chore: quick fix for 7.x docs buildchore: fix docs search generation for 8.x releasechore: use 8.x as default search versionstyle: fix lint from merge issuesMerge branch '7.x'chore: improve 7.x docs deploy scriptchore: add publish script for 7.xchore: release 7.6.5Merge pull request #14023 from rbjb/feat/add-uuid-typesMerge pull request #14028 from ruxxzebre/fix-tinstancemethod-thisMerge pull request #14042 from meabed/fix-index-aliasMerge pull request #14066 from Automattic/vkarpov15/gh-13977Merge pull request #14067 from Automattic/vkarpov15/gh-14062Merge pull request #14068 from Automattic/IslandRhythms/gh-14055test: fix tests re: #14076Merge pull request #14076 from ffflorian/fix/remove-counttrue fixfix: Remove count() from TypeScript definitionsMerge pull request #14065 from MuhibAhmed/patch-1Update schema.jstypes(model+query): correctly remove count from TypeScript types to reflect removal of runtime supportfix: handle update validators and single nested doc with numberic pathsUpdate queries.mdUpdate schema.jsone failing testMerge branch '6.x' into 7.xchore: publish 6.x under 6x tagchore: release 6.12.3Merge pull request #14053 from Automattic/vkarpov15/gh-14022Merge pull request #14052 from Automattic/vkarpov15/gh-14049feat: add Types.UUID typingstest: remove unused var re: code review commentsMerge branch '6.x' into vkarpov15/gh-14049Merge pull request #14047 from Automattic/vkarpov15/gh-14026test: add extra test case re: code review commentsfix(document): consistently avoid marking subpaths of nested paths as modifiedMerge branch '6.x' into vkarpov15/gh-14022test: fix testsfix(document): avoid unmarking modified on nested path if no initial value stored and already modifiedtest: typo fixtest: correctly work around lack of elvis operator in node v2 for #13085 testtest: fix tests re: #13085fix(ChangeStream): correctly handle `hydrate` option when using change stream as stream instead of iteratorMerge branch 'master' of github.com:Automattic/mongooseadd this context to statics + testfix: diffIndexes treats namespace error as emptytypes(model+query): unpack arrays in distinct return typeUpdate utils.jsrename object key in index without changing it's positionRename index object keys with alias and keeping it's positionsMerge pull request #14038 from Automattic/dependabot/npm_and_yarn/master/webpack-5.89.0Merge pull request #14037 from Automattic/dependabot/npm_and_yarn/master/sinon-17.0.1Merge pull request #14033 from Automattic/dependabot/npm_and_yarn/master/babel/core-7.23.2Merge pull request #14032 from Automattic/dependabot/npm_and_yarn/master/eslint-8.52.0Merge pull request #14031 from Automattic/dependabot/github_actions/master/actions/setup-node-4.0.0Merge pull request #14030 from Automattic/dependabot/github_actions/master/actions/checkout-4.1.1Merge pull request #14029 from Automattic/IslandRhythms/gh14010add test for schema methods typing scenarioadd intersection with AnyObjectuse decoration on methods property of Schema classchore(deps-dev): bump webpack from 5.88.2 to 5.89.0chore(deps-dev): bump sinon from 16.0.0 to 17.0.1chore(deps-dev): bump @babel/core from 7.23.0 to 7.23.2chore(deps-dev): bump eslint from 8.50.0 to 8.52.0chore(deps): bump actions/setup-node from 3.8.1 to 4.0.0chore(deps): bump actions/checkout from 4.1.0 to 4.1.1fix: diffIndexes treats namespace error as emptyuse decoration on methods schema optionadd type decoration utilitiesMerge pull request #14021 from Automattic/vkarpov15/gh-14020docs: fix migration guide linkdocs: use 8.x as default for search👉 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