build(deps-dev): bump mint from 4.2.741 to 4.2.772

[dependabot]

Bumps mint from 4.2.741 to 4.2.772.

Commits

• See full diff in compare view

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	mint@​4.2.741 ⏵ 4.2.772

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm @mintlify/cli under Elastic-2.0 License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: package-lock.json → npm/mint@4.2.772 → npm/@mintlify/cli@4.0.1375 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mintlify/cli@4.0.1375. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm @mintlify/common under ISC License: ISC - The applicable license policy does not permit this license (5) (npm metadata) License: ISC - The applicable license policy does not permit this license (5) (package/package.json) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: package-lock.json → npm/mint@4.2.772 → npm/@mintlify/common@1.0.1068 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mintlify/common@1.0.1068. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm @mintlify/link-rot under Elastic-2.0 License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: package-lock.json → npm/mint@4.2.772 → npm/@mintlify/link-rot@3.0.1265 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mintlify/link-rot@3.0.1265. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Publisher changed: npm @mintlify/mdx is now published by dks333 Author: dks333 From: package-lock.json → npm/mint@4.2.772 → npm/@mintlify/mdx@4.0.1 ℹ Read more on: This package | This alert | What is unstable ownership? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mintlify/mdx@4.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm @mintlify/models under Elastic-2.0 License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: package-lock.json → npm/mint@4.2.772 → npm/@mintlify/models@0.0.344 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mintlify/models@0.0.344. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm @mintlify/prebuild under Elastic-2.0 License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: package-lock.json → npm/mint@4.2.772 → npm/@mintlify/prebuild@1.0.1219 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mintlify/prebuild@1.0.1219. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm @mintlify/previewing under Elastic-2.0 License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: package-lock.json → npm/mint@4.2.772 → npm/@mintlify/previewing@4.0.1289 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mintlify/previewing@4.0.1289. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm @mintlify/scraping under Elastic-2.0 License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: package-lock.json → npm/mint@4.2.772 → npm/@mintlify/scraping@4.0.935 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mintlify/scraping@4.0.935. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm @mintlify/validation under Elastic-2.0 License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json) From: package-lock.json → npm/mint@4.2.772 → npm/@mintlify/validation@0.1.814 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mintlify/validation@0.1.814. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm mint under Elastic-2.0 License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json) License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: package-lock.json → npm/mint@4.2.772 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/mint@4.2.772. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.