[dependabot]

Bumps the dependencies group with 3 updates: i18next, react-i18next and amqplib.

Updates i18next from 26.5.12 to 26.6.0

Release notes

Sourced from i18next's releases.

v26.6.0

• feat(types): new strictInterpolationChecks type option (default false). With strictInterpolationChecks: true in CustomTypeOptions, t() needs its options for a string with {{variables}}: for 'Hello {{name}}!', t('greeting') is a type error and t('greeting', { name }) compiles. Left out, the variable reaches the UI as the raw {{name}} placeholder. This applies to string keys, selectors, selector arrays and getFixedT, and with strictKeyChecks also to t(key, defaultValue). Without the flag nothing changes. With the flag on, a wrapper that passes on a key type ((key: ParseKeys<'ns'>) => t(key), or a generic K extends ParseKeys) no longer compiles without options, as the variables of its string are not known there. parseInterpolation: 'icu' and 'mf2' require their arguments as before. Thanks @​Alex0007 (#2465).
• fix(types): an array of selectors with a plural member now requires count, as a single selector does since v25.9.0. Without count, i18next skips the plural member at runtime, so t([($) => $.item, ($) => $.plain]) returned the plain value while typed as the plural forms. An array of selectors with defaultValue now returns the literal values and the default value ('a' | 'b' | 'x') instead of string. Thanks @​Alex0007 (#2465).

Changelog

Sourced from i18next's changelog.

26.6.0

• feat(types): new strictInterpolationChecks type option (default false). With strictInterpolationChecks: true in CustomTypeOptions, t() needs its options for a string with {{variables}}: for 'Hello {{name}}!', t('greeting') is a type error and t('greeting', { name }) compiles. Left out, the variable reaches the UI as the raw {{name}} placeholder. This applies to string keys, selectors, selector arrays and getFixedT, and with strictKeyChecks also to t(key, defaultValue). Without the flag nothing changes. With the flag on, a wrapper that passes on a key type ((key: ParseKeys<'ns'>) => t(key), or a generic K extends ParseKeys) no longer compiles without options, as the variables of its string are not known there. parseInterpolation: 'icu' and 'mf2' require their arguments as before. Thanks @​Alex0007 (#2465).
• fix(types): an array of selectors with a plural member now requires count, as a single selector does since v25.9.0. Without count, i18next skips the plural member at runtime, so t([($) => $.item, ($) => $.plain]) returned the plain value while typed as the plural forms. An array of selectors with defaultValue now returns the literal values and the default value ('a' | 'b' | 'x') instead of string. Thanks @​Alex0007 (#2465).

Commits

• 3b43f2c 26.6.0
• 947ab51 changelog for 26.6.0
• 89d10cc changelog for unreleased #2465
• da9417a feat(types): strictInterpolationChecks requires t() options for a string with...
• See full diff in compare view

Updates react-i18next from 17.1.9 to 17.1.10

Changelog

Sourced from react-i18next's changelog.

17.1.10

• fix(Trans): markup inside an interpolated value is no longer parsed as translation markup. Trans interpolates values (and count, values in tOptions, or the whole string when there are no children) before it parses the string. With interpolation.escapeValue: false, or with an i18nFormat plugin (i18next-icu, i18next-mf2, i18next-fluent), which inserts values without escaping whatever escapeValue says, a value like <0 href="https://example.com">x</0> was rendered as component 0 with that href, overriding the props of the component, and <strong>x</strong> in a value became a real <strong>. Trans now escapes the values for this t() call (with a plugin, the string values in values) and decodes the entities after parsing, so such a value renders as text, and a " in a value no longer closes an attribute like <Item title="{{name}}" />. {{- var}} stays the explicit way for a translator to insert a value unescaped. As with shouldUnescape, entities written in these translations (for example &) are now decoded instead of shown literally. Output with escapeValue: true and no plugin, with i18next-icu escapeVariables: true, and with children and no values or count is unchanged.
• fix(IcuTrans): the same for IcuTrans with escapeValue: false or an i18nFormat plugin: a value like <0>x</0> no longer becomes the first component, and a value containing an entity like & is no longer decoded a second time.

Commits

• 983f586 17.1.10
• 7c86836 build
• 26c5467 fix(Trans, IcuTrans): don't parse markup that comes from interpolated values
• 16a017e docs: add Socket badge to README
• See full diff in compare view

Updates amqplib from 2.2.0 to 2.2.1

Changelog

Sourced from amqplib's changelog.

v2.2.1

• Return the server acknowledgement from promise-based channel.cancel, matching the callback API (thanks @​edsonsims).
• Type cancel replies as Replies.Cancel ({ consumerTag }) in both the promise and callback API declarations, which previously claimed Replies.Empty.
• Fix callback-based waitForConfirms never calling back when invoked after the confirm channel closed with unconfirmed messages; it now yields a channel closed error, matching the promise API (thanks @​youdie006).
• waitForConfirms (both APIs) now always fails with channel closed after the channel closes with unconfirmed messages. Previously it reported success if every outstanding message had its own callback, or on any call after the first.
• The callback API's waitForConfirms callback is now required in the TypeScript declarations, matching the docs. Calling it without one threw at runtime.
• Replace .npmignore with a files allowlist in package.json so the published package no longer includes tests, tooling config, dotfiles or the defs generator. Install size drops from 577 kB to 358 kB (fixes #859, thanks @​rubiesonthesky)

Commits

• 0bf17a0 2.2.1
• 1d38517 Prepare changelog for v2.2.1
• f5696a3 Merge pull request #863 from amqp-node/fix/npm-package-files
• 8fd6bbf Merge remote-tracking branch 'origin/main' into fix/npm-package-files
• 4762f75 Share waitForConfirms between APIs and fail consistently after close
• 8861ce4 Merge pull request #865 from youdie006/callback-wait-for-confirms-closed
• 9f739bf Fix callback waitForConfirms hanging after the channel closes
• 64f924f Type cancel replies as Replies.Cancel and simplify Channel#cancel
• d63ac20 Merge pull request #864 from edsonsims/fix/promise-cancel-acknowledgement
• f139242 fix: return cancellation acknowledgement from promise API
• Additional commits viewable 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