Skip to content

Update dependency @azure/msal-browser to v5#25

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/azure-msal-browser-5.x
Open

Update dependency @azure/msal-browser to v5#25
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/azure-msal-browser-5.x

Conversation

@renovate

@renovate renovate Bot commented May 14, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@azure/msal-browser ^4.25.0^5.0.0 age confidence

Configuration

📅 Schedule: (in timezone Europe/Oslo)

  • Branch creation
    • "before 07:00 on Thursday"
  • 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 was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented May 14, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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: oed-admin.client/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @azure/msal-react@3.0.20
npm error Found: @azure/msal-browser@5.17.1
npm error node_modules/@azure/msal-browser
npm error   @azure/msal-browser@"^5.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @azure/msal-browser@"^4.24.0" from @azure/msal-react@3.0.20
npm error node_modules/@azure/msal-react
npm error   @azure/msal-react@"^3.0.20" from the root project
npm error
npm error Conflicting peer dependency: @azure/msal-browser@4.30.0
npm error node_modules/@azure/msal-browser
npm error   peer @azure/msal-browser@"^4.24.0" from @azure/msal-react@3.0.20
npm error   node_modules/@azure/msal-react
npm error     @azure/msal-react@"^3.0.20" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-07-25T19_01_02_575Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-25T19_01_02_575Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/azure-msal-browser-5.x branch 2 times, most recently from 0391f4e to 23ce486 Compare May 24, 2026 14:57
@renovate
renovate Bot force-pushed the renovate/azure-msal-browser-5.x branch 2 times, most recently from bdc1465 to 246aed0 Compare June 1, 2026 14:10
@renovate
renovate Bot force-pushed the renovate/azure-msal-browser-5.x branch 2 times, most recently from f34a47e to 6509864 Compare June 12, 2026 07:54
@renovate
renovate Bot force-pushed the renovate/azure-msal-browser-5.x branch 2 times, most recently from fc2998b to ef6a893 Compare July 4, 2026 02:56
@renovate
renovate Bot force-pushed the renovate/azure-msal-browser-5.x branch from ef6a893 to d21055b Compare July 12, 2026 00:15
@renovate
renovate Bot force-pushed the renovate/azure-msal-browser-5.x branch from d21055b to e2fbab6 Compare July 18, 2026 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants