⬆️ Update dependency i18next to v23

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
i18next (source)	^22.5.1 -> ^23.0.0

---

Release Notes

i18next/i18next (i18next)

v23.2.11

Compare Source

• types: Fix $TFunctionBrand 1997

v23.2.10

Compare Source

• types: emit function can have additional arguments 1993

v23.2.9

Compare Source

• types: Add brand to TFunction type so different namespaces' TFunctions are not treated as compatible 1994

v23.2.8

Compare Source

• types for hasLoadedNamespace

v23.2.7

Compare Source

• fix utils import (for Deno)

v23.2.6

Compare Source

• Re-allow unknown keys, when a defaultValue is provided 1867

v23.2.5

Compare Source

• Clean language code before passing to formatters 1988

v23.2.3

Compare Source

• types: Optimize logic for fallback ns 1984

v23.2.2

Compare Source

• types: try to fix fallbackNS type handling also for older TS version 1981

v23.2.1

Compare Source

• types: Fix $TFunctionBrand 1997

v23.2.0

Compare Source

• types: add fallbackNS type handling 1975

v23.1.0

Compare Source

• cloneInstance: introduce forkResourceStore 1974
• types: default argument values for ParseKeys type

v23.0.2

Compare Source

• refactor: static createInstance for wider browser support 1973

v23.0.1

Compare Source

• types: export ParseKeys

v23.0.0

Compare Source

This is a major breaking release:

• redesigned TypeScript types 1911

• removed setDebug function in the logger: 1954

• changed returnNull default to false 1885

• drop support for old browsers and Node.js < v12 1948

• ordinal plural keys are now prefixed with _ordinal to help translators (non-breaking, because of fallback) 1945

➡️ check out the migration guide

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
homarr	⬜️ Ignored (Inspect)	Visit Preview		Aug 12, 2023 7:20pm

[github-actions]

📦 Next.js Bundle Analysis for homarr

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	366.3 KB (🟡 +5.09 KB)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Four Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/	96.85 KB (🔴 +21.51 KB)	463.15 KB
/[slug]	96.85 KB (🔴 +21.51 KB)	463.15 KB
/login	18.96 KB (🔴 +17.87 KB)	385.25 KB
/migrate	25.95 KB (🔴 +18.24 KB)	392.25 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 23.x releases. But if you manually upgrade to 23.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.