deps: Bump @azure/msal-node from 5.4.3 to 5.5.0

[dependabot]

Bumps @azure/msal-node from 5.4.3 to 5.5.0.

Release notes

Sourced from @​azure/msal-node's releases.

@​azure/msal-react v5.5.0

5.5.0

Tue, 23 Jun 2026 22:19:30 GMT

Minor changes

• Match the updated msal-browser AuthError signature #8609 (sameera.gajjarapu@microsoft.com)
• Bump @​azure/msal-browser to v5.15.0 (beachball)

@​azure/msal-node v5.5.0

5.5.0

Tue, 04 Aug 2026 20:17:38 GMT

Minor changes

• Add claimsFromClient request parameter to forward client-originated claims to IDP #8686 (rginsburg@microsoft.com)
• Bump @​azure/msal-common to v16.12.0 (beachball)

Patches

• Add attribute-tokens support #8700 (spingale@microsoft.com)
• Use length-prefix encoding for the additional cache key hash to prevent credential cache-key collisions #8713 (nichoudhary@microsoft.com)

@​azure/msal-react v5.4.5

5.4.5

Tue, 16 Jun 2026 19:46:35 GMT

Patches

• Bump @​azure/msal-browser to v5.14.0 (beachball)

@​azure/msal-react v5.4.4

5.4.4

Wed, 10 Jun 2026 22:41:34 GMT

Patches

• Bump @​azure/msal-browser to v5.13.0 (beachball)

Commits

• 5c53ac6 feat: add AttributeToken request and cache partition support (#8700)
• 7d10e6c  [NAA/PWB One Bridge] PR 1/6: webBrokerBridge scaffold — shared interfaces, e...
• 529fdd3 fix(msal-node): use length-prefix encoding for additional cache key hash to p...
• 006de72 Add clientClaims request parameter for confidential client (#8686)
• 2796e9b Bump uuid from 8.3.2 to 14.0.0 (#8575)
• 45ac206 Bump immutable from 5.1.7 to 5.1.9 (#8718)
• 8c1ec2d Bump webpack-dev-server from 5.2.3 to 5.2.6 (#8716)
• cd19b1a Bump postcss from 8.5.15 to 8.5.18 (#8730)
• 86bd093 test(e2e): shared brokering e2e helpers + real KMSI assertion (Foundation PR ...
• a6a32af Post-release PR (#8734)
• 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Gregory Joseph (gnjoseph)]

Dependabot triage: unsupported-major.

• Evidence: Security / audit failed at npm audit --audit-level=high (run). The recorded run reports high-severity nanoid and brace-expansion advisories. Revalidation against the current advisory DB gives nanoid <3.3.18 (GHSA-2v37-7h3g-55p8) with No fix available. The compatible chain is vitest -> vite -> postcss@8.5.x -> nanoid@^3.3.17; PostCSS 8.5.26 still declares nanoid: ^3.3.17, the registry's newest 3.x is 3.3.17, and nanoid@6.0.1 is outside that constraint. brace-expansion can move to 5.0.9, but the nanoid gate remains unsatisfied.
• Action: defer and close this bump. No major override, --legacy-peer-deps, or check bypass will be used.
• Unblock condition: recreate/reopen after either a compatible nanoid >=3.3.18 is published or PostCSS/Vite moves to a safe nanoid line, and Security / audit passes.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.