chore(deps): bump nuxt-og-image from 5.1.12 to 6.2.5

[dependabot]

Bumps nuxt-og-image from 5.1.12 to 6.2.5.

Release notes

Sourced from nuxt-og-image's releases.

v6.2.5

   🐞 Bug Fixes

• Hydration-issue warning due to SSR generated DateTime value  -  by @​khatastroffik in nuxt-modules/og-image#535 (92d9d)
• Sanitize component props  -  by @​harlan-zw in nuxt-modules/og-image#543 (3dcf8)
• Harden security defaults  -  by @​harlan-zw in nuxt-modules/og-image#540 (9902a)
• Whitelist component props to prevent cache key DoS  -  by @​harlan-zw in nuxt-modules/og-image#544 (bd05a)

    View changes on GitHub

v6.2.4

   🐞 Bug Fixes

• Burst cache when og image templates change  -  by @​harlan-zw (0b817)
• Drop query param build id cache bursting  -  by @​harlan-zw (851b1)

    View changes on GitHub

v6.2.3

   🐞 Bug Fixes

• cloudflare: Detect legacy assets mode  -  by @​harlan-zw (7f60a)

   🏎 Performance

• devtools: Drop json-editor-vue  -  by @​harlan-zw (14a58)

    View changes on GitHub

v6.2.2

No significant changes

    View changes on GitHub

v6.2.1

   🐞 Bug Fixes

• Missing compatibility config  -  by @​harlan-zw (45410)
• devtools: Broken resolution  -  by @​harlan-zw (57ac2)

    View changes on GitHub

v6.2.0

   🚀 Features

• content: Add defineOgImageSchema() composable  -  by @​harlan-zw in nuxt-modules/og-image#520 (e9cde)

   🐞 Bug Fixes

• Update pnpm-lock.yaml  -  by @​harlan-zw (0784c)

... (truncated)

Commits

• 29b68f1 chore: release v6.2.5
• e7deb1f chore: sync
• bd05a77 fix: whitelist component props to prevent cache key DoS (#544)
• 9902a89 fix: harden security defaults (#540)
• 3dcf8c1 fix: sanitize component props (#543)
• 284540a chore: artifact
• bcad791 chore: bump deps
• a8a65b6 chore: bump deps
• 92d9dac fix: hydration-issue warning due to SSR generated DateTime value (#535)
• 10c5453 chore: release v6.2.4
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	nuxt-og-image@​5.1.12 ⏵ 6.2.5	-2	+4	+3	+1

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 lru-cache under BlueOak-1.0.0 License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (npm metadata) License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/package.json) License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/LICENSE.md) From: pnpm-lock.yaml → npm/lru-cache@11.2.7 ℹ 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/lru-cache@11.2.7. 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		Obfuscated code: npm markdown-it is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/markdown-it@14.1.1 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/markdown-it@14.1.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.

View full report