chore(deps): bump the production-dependencies group with 24 updates

[dependabot]

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[greptile-apps]

PR author is in the excluded authors list.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	posthog-js@​1.399.2
	@​tanstack/​react-virtual@​3.14.6
	hono@​4.12.30
	@​tanstack/​virtual-core@​3.17.4
	add-mcp@​1.14.0
	@​sentry/​browser@​10.65.0
	posthog-node@​5.41.0
	lucide-react@​1.24.0
	@​types/​three@​0.185.1
	@​babel/​parser@​8.0.4
	@​astrojs/​cloudflare@​14.1.2
	tailwindcss@​4.3.2
	@​astrojs/​starlight@​0.41.3
	astro@​7.0.7
	typescript@​7.0.2
	@​ungap/​structured-clone@​1.3.3
	@​tailwindcss/​vite@​4.3.2
	shadcn@​4.13.0
	whatwg-url@​16.0.1 ⏵ 17.1.0			+1	-3
	@​hono/​mcp@​0.3.1
	three@​0.185.1
	sharp@​0.35.3
	@​hono/​node-server@​2.0.8
	@​sentry/​node@​10.65.0
	graphql@​17.0.2

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		Obfuscated code: npm astro is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: apps/catalog/package.json → npm/astro@7.0.7 ℹ 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/astro@7.0.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.

View full report