fix(deps): update dependency i18next to ^26.3.1 #16

Closed

Renovate wants to merge 342 commits from renovate/i18next-26.x into main

pull from: renovate/i18next-26.x

merge into: kreativmonkey:main

kreativmonkey:main

kreativmonkey:renovate/frontend-non-major-dependencies

kreativmonkey:renovate/website-non-major-dependencies

kreativmonkey:renovate/modernc.org-sqlite-1.x

kreativmonkey:renovate/actions-setup-go-7.x

kreativmonkey:renovate/actions-setup-node-7.x

kreativmonkey:renovate/github.com-mmcdole-gofeed-1.x

kreativmonkey:renovate/github.com-coreos-go-oidc-v3-3.x

kreativmonkey:renovate/typescript-7.x

kreativmonkey:dev

kreativmonkey:renovate/lock-file-maintenance

kreativmonkey:feat/agent-tools-registry

kreativmonkey:feat/ai-prompt-hardening

kreativmonkey:feature/frontend-update-2026-v2

kreativmonkey:feat/instance-migration

kreativmonkey:fix/recurring-posting-time

kreativmonkey:fix/ai-truncation-retry

kreativmonkey:feat/recurring-posts-edit-counter-ai

kreativmonkey:feature/ai-addon

Conversation 1 Commits 342 Files changed 404 +1 -1

Renovate commented 2026-06-08 22:01:59 +02:00

Collaborator

Copy link

This PR contains the following updates:

Package	Change	Age	Confidence
i18next (source)	^26.2.0 → ^26.3.1

---

Release Notes

i18next/i18next (i18next)

v26.3.1

Compare Source

• fix(types): t() with a keyPrefix no longer pollutes its return type with sibling keys' values. A regression in 26.3.0 — the [Res] extends [never] guards added to KeysBuilderWithReturnObjects / KeysBuilderWithoutReturnObjects turned the builders into deferred conditional types, so KeyPrefix<Ns> stopped resolving to a literal union and keyPrefix inference widened to the whole namespace. Symptom: useTranslation(ns, { keyPrefix: 'a.b' }) then t('title') would resolve to '<a.b>.title' | '<other.path>.title' | ... instead of just the scoped value. Affected every react-i18next user using keyPrefix. Restored to the eager 26.2.0 form. The same-namespace conflict handling from #​2434 still works via _DropConflictKeys at the merge layer (in options.d.ts). Thanks @​aaronrosenthal (#​2436).

v26.3.0

Compare Source

• feat(types): introduce ResourceNamespaceMap — a separate mergeable augmentation surface for namespace resource types, designed for monorepos where multiple packages each want to contribute their own namespaces. Previously, every package had to coordinate on a single CustomTypeOptions.resources declaration (or fall back to typing dependency namespaces as any) because resources is a single property of an interface and TypeScript reports TS2717 when two declarations of the same property disagree. The new interface merges naturally across declare module 'i18next' blocks, so each package can ship its own i18next.d.ts independently. Per-property merge handles same-namespace contributions from multiple packages, and same-key/different-literal conflicts are silently dropped to avoid poisoning t() overload resolution. Fully backwards-compatible — existing CustomTypeOptions.resources augmentations continue to work, and both surfaces can coexist. Scalar options (defaultNS, returnNull, enableSelector, etc.) still belong on CustomTypeOptions. Thanks @​sh3xu (#​2434). Fixes #​2409.

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

• 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.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [i18next](https://www.i18next.com) ([source](https://github.com/i18next/i18next)) | [`^26.2.0` → `^26.3.1`](https://renovatebot.com/diffs/npm/i18next/26.2.0/26.3.1) |  |  | --- ### Release Notes <details> <summary>i18next/i18next (i18next)</summary> ### [`v26.3.1`](https://github.com/i18next/i18next/blob/HEAD/CHANGELOG.md#2631) [Compare Source](https://github.com/i18next/i18next/compare/v26.3.0...v26.3.1) - fix(types): `t()` with a `keyPrefix` no longer pollutes its return type with sibling keys' values. A regression in 26.3.0 — the `[Res] extends [never]` guards added to `KeysBuilderWithReturnObjects` / `KeysBuilderWithoutReturnObjects` turned the builders into deferred conditional types, so `KeyPrefix<Ns>` stopped resolving to a literal union and `keyPrefix` inference widened to the whole namespace. Symptom: `useTranslation(ns, { keyPrefix: 'a.b' })` then `t('title')` would resolve to `'<a.b>.title' | '<other.path>.title' | ...` instead of just the scoped value. Affected every `react-i18next` user using `keyPrefix`. Restored to the eager 26.2.0 form. The same-namespace conflict handling from [#&#8203;2434](https://github.com/i18next/i18next/issues/2434) still works via `_DropConflictKeys` at the merge layer (in `options.d.ts`). Thanks [@&#8203;aaronrosenthal](https://github.com/aaronrosenthal) ([#&#8203;2436](https://github.com/i18next/i18next/pull/2436)). ### [`v26.3.0`](https://github.com/i18next/i18next/blob/HEAD/CHANGELOG.md#2630) [Compare Source](https://github.com/i18next/i18next/compare/v26.2.0...v26.3.0) - feat(types): introduce `ResourceNamespaceMap` — a separate mergeable augmentation surface for namespace resource types, designed for monorepos where multiple packages each want to contribute their own namespaces. Previously, every package had to coordinate on a single `CustomTypeOptions.resources` declaration (or fall back to typing dependency namespaces as `any`) because `resources` is a single property of an interface and TypeScript reports TS2717 when two declarations of the same property disagree. The new interface merges naturally across `declare module 'i18next'` blocks, so each package can ship its own `i18next.d.ts` independently. Per-property merge handles same-namespace contributions from multiple packages, and same-key/different-literal conflicts are silently dropped to avoid poisoning `t()` overload resolution. Fully backwards-compatible — existing `CustomTypeOptions.resources` augmentations continue to work, and both surfaces can coexist. Scalar options (`defaultNS`, `returnNull`, `enableSelector`, etc.) still belong on `CustomTypeOptions`. Thanks [@&#8203;sh3xu](https://github.com/sh3xu) ([#&#8203;2434](https://github.com/i18next/i18next/pull/2434)). Fixes [#&#8203;2409](https://github.com/i18next/i18next/issues/2409). </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/Berlin) - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTMuMyIsInVwZGF0ZWRJblZlciI6IjQzLjIxMy4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Renovate commented 2026-06-08 22:02:00 +02:00

Author

Collaborator

Copy link

⚠️ 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: frontend/pnpm-lock.yaml

 ERR_PNPM_ABORTED_REMOVE_MODULES_DIR_NO_TTY  Aborted removal of modules directory due to no TTY

If you are running pnpm in CI, set the CI environment variable to "true", or set "confirmModulesPurge" to "false".

### ⚠️ 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: frontend/pnpm-lock.yaml ```  ERR_PNPM_ABORTED_REMOVE_MODULES_DIR_NO_TTY  Aborted removal of modules directory due to no TTY If you are running pnpm in CI, set the CI environment variable to "true", or set "confirmModulesPurge" to "false". ```

Renovate added 1 commit 2026-06-08 22:02:09 +02:00

fix(deps): update dependency i18next to ^26.3.1 6f10dfa377

Renovate force-pushed renovate/i18next-26.x from 6f10dfa377 to a9c00f5948 2026-06-09 02:02:42 +02:00 Compare

Renovate force-pushed renovate/i18next-26.x from a9c00f5948 to 7464a97062 2026-06-09 06:02:33 +02:00 Compare

kreativmonkey closed this pull request 2026-06-09 15:33:13 +02:00

kreativmonkey referenced this pull request from a commit 2026-06-17 09:09:33 +02:00

fix(analytics): rename misleading reach metric to network size (issue #16)

kreativmonkey referenced this pull request from a commit 2026-06-27 08:54:30 +02:00

chore(main): release 0.1.1 (#4)

kreativmonkey referenced this pull request from a commit 2026-06-27 08:54:31 +02:00

chore(main): release 0.1.2 (#16)

Some checks failed

Hide all checks

renovate/artifacts Artifact file update failure

CI/CD Workflow / E2E (Playwright + Go) (pull_request) Failing after 36s

Details

CI/CD Workflow / Test Backend (Go) (pull_request) Successful in 2m20s

Details

CI/CD Workflow / Test Frontend (Node.js) (pull_request) Failing after 15s

Details

CI/CD Workflow / Build and Publish Docker Image (pull_request) Has been skipped

Details

CI/CD Workflow / Trigger Dockhand Deployment (pull_request) Has been skipped

Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

wontfix

This won't be fixed

No labels

bug

duplicate

enhancement

help wanted

invalid

question

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

kreativmonkey/goloom!16

No description provided.