chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

Review

• Updates have been tested and work
• If updates are AWS related, versions match the infrastructure (e.g. Lambda runtime, database, etc.)

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - "before 6am on the first day of the month" in timezone America/Montreal, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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 artifacts 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: utils/angular-output-target/package-lock.json

undefined

File name: packages/web/package-lock.json

undefined

File name: packages/vue/package-lock.json

undefined

File name: packages/react/package-lock.json

undefined

File name: packages/react-ssr/package-lock.json

undefined

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: [email protected]
npm error Found: @angular/[email protected]
npm error node_modules/@angular/core
npm error   @angular/core@"^19.2.15" from the root project
npm error   peer @angular/core@"19.2.15" from @angular/[email protected]
npm error   node_modules/@angular/animations
npm error     @angular/animations@"^19.2.15" from the root project
npm error     peerOptional @angular/animations@"19.2.15" from @angular/[email protected]
npm error     node_modules/@angular/platform-browser
npm error       dev @angular/platform-browser@"^19.2.15" from the root project
npm error       1 more (@angular/forms)
npm error   4 more (@angular/common, @angular/forms, ...)
npm error
npm error Could not resolve dependency:
npm error dev @angular-devkit/build-angular@"^19.2.15" from the root project
npm error
npm error Conflicting peer dependency: @angular/[email protected]
npm error node_modules/@angular/core
npm error   peer @angular/core@"19.2.16" from @angular/[email protected]
npm error   node_modules/@angular/service-worker
npm error     peerOptional @angular/service-worker@"^19.0.0 || ^19.2.0-next.0" from @angular-devkit/[email protected]
npm error     node_modules/@angular-devkit/build-angular
npm error       dev @angular-devkit/build-angular@"^19.2.15" 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/2025-11-26T21_49_17_860Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-26T21_49_17_860Z-debug-0.log