chore(deps): update dependency nanoid@>=4.0.0 <5.0.9 to >=5.1.16

[homarr-renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
nanoid@>=4.0.0 <5.0.9	[>=5.1.15 → >=5.1.16](https://renovatebot.com/diffs/npm/nanoid@>=4.0.0 <5.0.9/5.1.15/5.1.16)

---

Release Notes

ai/nanoid (nanoid@>=4.0.0 <5.0.9)

v5.1.16

Compare Source

• Fixed forever loop on negative size (by @​spokodev).

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[dokploy-homarr-labs]

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

• User: homarr-renovate[bot]
• Repository: homarr
• Permission Level: none
• Required Level: write, maintain, or admin

How to resolve this:

Option 1: Get Collaborator Access (Recommended)
Ask a repository maintainer to invite you as a collaborator with write permissions or higher.

Option 2: Request Permission Override
Ask a repository administrator to disable security validation for this specific application if appropriate.

For Repository Administrators:

To disable this security check (⚠️ not recommended for public repositories):
Enter to preview settings and disable the security check.

---

This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments.

🛡️ Learn more about this security feature

This protection prevents unauthorized users from:

• Executing malicious code on the deployment server
• Accessing environment variables and secrets
• Potentially compromising the infrastructure

Preview deployments are powerful but require trust. Only users with repository write access can trigger them.

[homarr-approvals]

Automatically approved by GitHub Action

[homarr-approvals]

Automatically approved by GitHub Action