fix(deps): patch framework and authentication dependencies - #93
Open
Bircck wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Depends on #92. This PR targets
fix/dependency-maintenanceto show only the runtime changes. After #92 merges, retarget this PR tomainand rerun CI before merging.Update Next.js to 15.5.25, Auth.js to 5.0.0-beta.32, Azure Identity to 4.13.1, and Sharp to 0.35.4. Keep React, MUI and generator dependencies unchanged. Use a scoped PostCSS 8.5.28 override for Next.js 15 and remove its stale nested lockfile entry. The final npm audit reports zero findings.
This is a separate batch from utility maintenance because authentication and native image-processing changes require additional integration validation. Azure Identity's patch includes a transitive MSAL major-version change. Document version choices and the override's removal condition.
Validation: clean npm ci, lint and production build on Node 22.23.2; packaged standalone HTTP checks for password validation, synthetic sessions, protected-page access, assets and logout; native Sharp PNG/WebP/AVIF operations. Linux native entries remain in the lockfile.
Before merge: Linux CI, visual/browser checks, live Entra ID sign-in and allowed/denied group access, Azure identity/wiki integration, and a complete canary refresh/deploy cycle. Existing daily consumers must pin a reviewed source revision in their own pipelines; a release tag alone does not gate deployment.
CI also runs for pull requests targeting stacked branches.