fix(deps): update openmfp and platform mesh

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@openmfp/eslint-config-typescript	0.7.7 → 0.7.9
@openmfp/eslint-config-typescript	0.7.8 → 0.7.9
@openmfp/portal-server-lib	0.163.7 → 0.163.8
@openmfp/portal-ui-lib	0.185.1 → 0.185.2
@platform-mesh/portal-server-lib	0.5.42 → 0.5.43
@platform-mesh/portal-ui-lib	0.24.7 → 0.24.9

---

Release Notes

openmfp/typescript-configs (@​openmfp/eslint-config-typescript)

v0.7.9

Compare Source

v0.7.8

Compare Source

openmfp/portal-server-lib (@​openmfp/portal-server-lib)

v0.163.8

Compare Source

openmfp/portal-ui-lib (@​openmfp/portal-ui-lib)

v0.185.2

Compare Source

platform-mesh/portal-server-lib (@​platform-mesh/portal-server-lib)

v0.5.43

Compare Source

platform-mesh/portal-ui-lib (@​platform-mesh/portal-ui-lib)

v0.24.9

Compare Source

v0.24.8

Compare Source

---

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.

👻 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 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: frontend/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 unable to resolve dependency tree
npm error
npm error While resolving: frontend@0.0.0
npm error Found: @angular/cli@20.3.13
npm error node_modules/@angular/cli
npm error   dev @angular/cli@"20.3.13" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/cli@">= 21.0.0 < 22.0.0" from angular-eslint@21.1.0
npm error node_modules/angular-eslint
npm error   peer angular-eslint@"^20.5.0 || ^21.0.0" from @openmfp/eslint-config-typescript@0.7.9
npm error   node_modules/@openmfp/eslint-config-typescript
npm error     dev @openmfp/eslint-config-typescript@"0.7.9" 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-01-05T21_11_38_552Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-05T21_11_38_552Z-debug-0.log

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.