[Snyk] Upgrade mongoose from 6.7.2 to 6.7.3

[maidul98]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade mongoose from 6.7.2 to 6.7.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.
• The recommended version was released 22 days ago, on 2022-11-22.

Release notes

Package name: mongoose

• 6.7.3 - 2022-11-22
  

  6.7.3 / 2022-11-22

  • fix(document): handle setting array to itself after saving and pushing a new value #12672 #12656
  • fix(types): update replaceWith pipeline stage #12715 coyotte508
  • fix(types): remove incorrect modelName type definition #12682 #12669 lpizzinidev
  • fix(schema): fix setupTimestamps for browser.umd #12683 raphael-papazikas
  • docs: correct justOne description #12686 #12599 tianguangcn
  • docs: make links more consistent #12690 #12645 hasezoey
  • docs(document): explain that $isNew is false in post('save') hooks #12685 #11990
  • docs: fixed line causing a "used before defined" linting error #12707 sgpinkus
• 6.7.2 - 2022-11-07
  

  6.7.2 / 2022-11-07

  • fix(discriminator): skip copying base schema plugins if applyPlugins == false #12613 #12604 lpizzinidev
  • fix(types): add UUID to types #12650 #12593
  • fix(types): allow setting SchemaTypeOptions' index property to IndexOptions #12562
  • fix(types): set this to doc type in SchemaType.prototype.validate() #12663 #12590
  • fix(types): correct handling for model #12659 #12573
  • fix(types): pre hook with deleteOne should resolve this as Query #12642 #12622 lpizzinidev

from mongoose GitHub release notes

Commit messages

Package name: mongoose

• e50de5c chore: release 6.7.3
• df7ea24 Merge pull request #12715 from coyotte508/patch-5
• 616ce5d Correctly prefix with $
• aa06f1d fix(types): Update replaceWith pipeline stage
• 15c0068 Merge pull request #12686 from Automattic/vkarpov15/gh-12599
• 4324a04 Merge pull request #12690 from hasezoey/updateRemainingLinks
• 294d85e Merge pull request #12705 from lpizzinidev/fix-mongoose-docs
• f989428 Merge pull request #12707 from sgpinkus/patch-1
• d4fca35 Merge pull request #12709 from lpizzinidev/gh-12706
• afbd8d1 docs(query): updated examples for updateOne and replaceOne
• b8f24f3 Replace used before defined User with this.
• 4f3c565 docs(mongoose): removed duplicated line
• 7a0a0ec docs: fix remaining static links
• 3e581f2 docs: update remaining links to use no-prefix relative links
• afc6022 docs(CONTRIBUTING): consistenize spacing
• 335e21c docs(CONTRIBUTING): add section for documentation style guidelines
• c6d3b16 docs(CONTRIBUTING): update documentation reference to ".pug" files
• a5d2acf docs: address code review comments re: #12599
• c77dd1b Merge pull request #12685 from Automattic/vkarpov15/gh-11990
• 349e038 style: fix lint
• 0c1ac69 Merge pull request #12623 from kevo1ution/fix-bad-docs-version
• ed6740f docs: fix inverted explanation of `justOne` option for populate
• 87d843d docs(document): explain that `$isNew` is `false` in post('save') hooks
• d98b285 Merge pull request #12672 from Automattic/vkarpov15/gh-12656

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
5324534	Generic High Entropy Secret	1863826	.env.example	View secret
5324535	Generic High Entropy Secret	1863826	.env.example	View secret
5324536	Generic High Entropy Secret	1863826	.env.example	View secret
5324537	Generic High Entropy Secret	1863826	.env.example	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>