[dependabot]

Bumps the production-patches group with 4 updates: @modelcontextprotocol/sdk, i18next, mongoose and react-i18next.

Updates @modelcontextprotocol/sdk from 1.32.1 to 1.32.2

Release notes

Sourced from @​modelcontextprotocol/sdk's releases.

1.32.2

What's Changed

• fix: add explicit | undefined to Transport optional properties (v1.x backport of #1766) by @​kishormorol in modelcontextprotocol/typescript-sdk#2814
• [v1.x] fix: allow registering after connect() when the capability was declared by @​claude[bot] in modelcontextprotocol/typescript-sdk#2958
• chore: bump version to 1.32.2 by @​claude[bot] in modelcontextprotocol/typescript-sdk#3089

New Contributors

• @​kishormorol made their first contribution in modelcontextprotocol/typescript-sdk#2814

Full Changelog: modelcontextprotocol/typescript-sdk@1.32.1...1.32.2

Commits

• 3b73021 chore: bump version to 1.32.2 (#3089)
• fa56d81 [v1.x] fix: allow registering after connect() when the capability was declare...
• 6919e95 fix: add explicit | undefined to Transport optional properties (v1.x backport...
• See full diff in compare view

Updates i18next from 26.5.6 to 26.5.7

Release notes

Sourced from i18next's releases.

v26.5.7

• fix: with the default cacheInBuiltFormats: true, built-in formats now also work when the t() options contain a BigInt or a circular object. The cache key was built with JSON.stringify over all options, including the interpolation values, which throws on those, so every built-in format in that call returned the raw value: t('num', { val: 12345678901234567890n }) with 'Total: {{val, number}}' returned 'Total: 12345678901234567890' instead of 'Total: 12,345,678,901,234,567,890', and passing an object with a back-reference (like an ORM entity) left all numbers, dates and lists of that call unformatted. When the key cannot be built, the value is now formatted without the cache, as with cacheInBuiltFormats: false. This also applies to formatters added with addCached. Other calls still use the cache as before. Thanks @​nk-batman21 (#2457).

Changelog

Sourced from i18next's changelog.

26.5.7

• fix: with the default cacheInBuiltFormats: true, built-in formats now also work when the t() options contain a BigInt or a circular object. The cache key was built with JSON.stringify over all options, including the interpolation values, which throws on those, so every built-in format in that call returned the raw value: t('num', { val: 12345678901234567890n }) with 'Total: {{val, number}}' returned 'Total: 12345678901234567890' instead of 'Total: 12,345,678,901,234,567,890', and passing an object with a back-reference (like an ORM entity) left all numbers, dates and lists of that call unformatted. When the key cannot be built, the value is now formatted without the cache, as with cacheInBuiltFormats: false. This also applies to formatters added with addCached. Other calls still use the cache as before. Thanks @​nk-batman21 (#2457).

Commits

• 21f3b52 26.5.7
• 35b1cf3 build
• d1ae940 changelog for 26.5.7
• 48ac091 fix: format values when cached formatter options are not serializable (#2457)
• See full diff in compare view

Updates mongoose from 9.11.3 to 9.11.4

Release notes

Sourced from mongoose's releases.

9.11.4 / 2026-10-23

• fix: avoid walking into inherited properties like toString when hydrating documents, setting dotted paths, and merging updates
• fix: only use own properties when looking up discriminators by key
• fix(schema): disallow setting special properties via virtual()
• fix(query): respect connection-level sanitizeFilter in queries
• fix(query): disallow special properties like __proto__ as paths in where() and mod()
• fix(deps): upgrade mquery -> 6.0.1 to avoid prototype pollution with query helpers like gt() and in()

Changelog

Sourced from mongoose's changelog.

9.11.4 / 2026-10-23

• fix: avoid walking into inherited properties like toString when hydrating documents, setting dotted paths, and merging updates
• fix: only use own properties when looking up discriminators by key
• fix(schema): disallow setting special properties via virtual()
• fix(query): respect connection-level sanitizeFilter in queries
• fix(query): disallow special properties like __proto__ as paths in where() and mod()
• fix(deps): upgrade mquery -> 6.0.1 to avoid prototype pollution with query helpers like gt() and in()

Commits

• 8d8b50f chore: release 9.11.4
• 1a95578 chore: bump mquery -> 6.0.1
• e339a2a Merge branch 'vkarpov15/20261022/master/security'
• 12058e0 Merge branch 'vkarpov15/20261016/master/security'
• b68f907 fix: only use own properties when looking up discriminators by key
• e681842 fix: skip inherited properties in setDottedPath - not user facing but still g...
• 2a195d1 fix: avoid setting values underneath inherited properties when constructing n...
• fc01d2f fix: avoid overriding built-in properties when copying conditions and avoid p...
• 74df776 fix: disallow setting special properties via virtual()
• 4bb6594 fix(query): respect connection-level sanitizeFilter in queries
• See full diff in compare view

Updates react-i18next from 17.1.3 to 17.1.5

Changelog

Sourced from react-i18next's changelog.

17.1.5

• fix(Trans): with an array of keys and no children, Trans now falls back to the last key when none of them has a translation, as t() does. It used the array itself as defaultValue, which i18next handles as an object, so <Trans i18nKey={['notifications.crm_item_created', 'crm_item_created']} components={[<strong />]} /> rendered key 'crm_item_created (en)' returned an object instead of string. instead of crm_item_created. An array of selectors falls back to the key of the last selector. The first key that has a translation still wins, and children, defaults and tOptions.defaultValue are used as before. With saveMissing, these calls now report the missing key, like a single i18nKey does. Thanks @​nk-batman21 (#1941).

17.1.4

• fix(types): without allowObjectInHTMLChildren, the children of HTML elements now use React's own type (DOMAttributes<T>['children']) instead of the ReactI18NextChildren | Iterable<ReactI18NextChildren> union. Both accept the same children, so nothing compiles differently. For default installs the global HTMLAttributes augmentation now repeats whatever @types/react declares, so changes in React's types flow through instead of meeting a copy, and type errors on element children no longer list an extra Iterable<...>. With allowObjectInHTMLChildren: true nothing changes. First step of #1928.

Commits

• 396dba9 17.1.5
• 3d18890 build
• c8a4924 changelog for 17.1.5
• 7724d5a fix(Trans): fall back to the last key of an i18nKey array, like t() (#1941)
• 290e8ab 17.1.4
• aeb94d1 changelog for 17.1.4
• 3fecad7 fix(types): use React's own children type unless allowObjectInHTMLChildren is...
• See full diff in compare view

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
pixelated	Ignored	Preview	Oct 27, 2026 3:11am UTC

[github-actions]

px Advisor Review

Risk: unknown

No summary available

No findings.

[github-actions]

Lighthouse CI Results

Routes audited: /, /dashboard?perf=1, /training-session

Thresholds: Performance ≥90 | Accessibility ≥90 | Best Practices ≥85

Reports

• lhr-1793070843920
• lhr-1793070855583
• lhr-1793070866843
• lhr-1793070877552
• lhr-1793070888161
• lhr-1793070898814
• lhr-1793070909476
• lhr-1793070920079
• lhr-1793070930725

Reports are also available as workflow artifacts