Update dependency oidc-client-ts from v3.3.0 to v3.5.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
oidc-client-ts	3.3.0 → 3.5.0

---

Release Notes

authts/oidc-client-ts (oidc-client-ts)

v3.5.0

Compare Source

oidc-client-ts v3.5.0 is a minor release.

No longer using crypto-js package, but built-in browser crypto.subtle module. Crypto.subtle is available only in secure contexts (HTTPS). Also have a look into the migration info.

Changelog:

• Features:
  • #​2295 add maxSilentRenewTimeoutRetries configuration
  • #​2311 add nonce validation for ID tokens
• Fixes;
  • #​2369 reword misleading error messages for request_type check

thanks to @​ninadvadujkar, @​Osmose and @​ferdinand-varta

v3.4.1

Compare Source

oidc-client-ts v3.4.1 is a bugfix release.

No longer using crypto-js package, but built-in browser crypto.subtle module. Crypto.subtle is available only in secure contexts (HTTPS). Also have a look into the migration info.

Changelog:

• Fixes:
  • #​2259 forward popupAbortOnClose to PopupNavigator.prepare

thanks to @​watabean

v3.4.0

Compare Source

oidc-client-ts v3.4.0 is a minor release.

No longer using crypto-js package, but built-in browser crypto.subtle module. Crypto.subtle is available only in secure contexts (HTTPS). Also have a look into the migration info.

Changelog:

• Features:
  • #​1890 optionally enforce iframe auth flow in signinSilent
  • #​2180 add support for client_secret_jwt
  • #​2244 optionally restore popup close rejection
• Fixes;
  • #​2147 wait until the page is shown again to resolve in RedirectNavigator

thanks to @​Hyperkid123, @​Nick-Source, @​Skizu and @​smujmaiku

---

Configuration

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

🚦 Automerge: Enabled.

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

[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: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @sentry/react@7.120.4
npm error Found: react@19.1.1
npm error node_modules/react
npm error   react@"19.1.1" from the root project
npm error   peer react@">=16.8.0" from @emotion/react@11.14.0
npm error   node_modules/@emotion/react
npm error     @emotion/react@"11.14.0" from the root project
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.14.1
npm error     node_modules/@emotion/styled
npm error       @emotion/styled@"11.14.1" from the root project
npm error       6 more (@mui/lab, @mui/material, @mui/styled-engine, ...)
npm error     6 more (@mui/lab, @mui/material, @mui/styled-engine, ...)
npm error   25 more (@emotion/styled, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"15.x || 16.x || 17.x || 18.x" from @sentry/react@7.120.4
npm error node_modules/@sentry/react
npm error   @sentry/react@"7.120.4" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"15.x || 16.x || 17.x || 18.x" from @sentry/react@7.120.4
npm error   node_modules/@sentry/react
npm error     @sentry/react@"7.120.4" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-14T13_08_33_129Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-14T13_08_33_129Z-debug-0.log