Update dependency i18next-resources-to-backend to v1.2.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
i18next-resources-to-backend	1.2.1 → 1.2.3

---

Release Notes

i18next/i18next-resources-to-backend (i18next-resources-to-backend)

v1.2.3

Compare Source

• fix: allow empty language/namespace strings again (e.g. defaultNS: ''), rejected since 1.2.2 #​16. An empty string cannot traverse the filesystem or reach Object.prototype, so it was never part of the attack surface.

v1.2.2

Compare Source

• security: validate language and namespace in read() before they are passed to the loader. i18next resolves any string as a language unless supportedLngs is set, so these values can carry whatever a language detector picked up from the querystring, path or a cookie. The documented usage pattern is import(./locales/${language}/${namespace}.json), and while a bundler compiles that template to a fixed context map, an unbundled ESM runtime (Node SSR) resolves the specifier against the filesystem, where a crafted value escapes the locales directory. Values containing .., \, control characters, __proto__ / constructor / prototype, or longer than 128 characters are now rejected with an error and the loader is never called; / is rejected for language but allowed for namespace, where nested layouts such as a/b are legitimate. The same check keeps the static-resources lookup off Object.prototype.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 4am on the first day of the month"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 was generated by Mend Renovate. View the repository job log.

[dokploy-2025-09-04-9e6xob]

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

• User: renovate[bot]
• Repository: sparked-next
• 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.