Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 13, 2025

This PR contains the following updates:

Package Change Age Confidence
@openmfp/eslint-config-typescript 0.7.70.7.11 age confidence

Release Notes

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

v0.7.11

Compare Source

v0.7.10

Compare Source

v0.7.9

Compare Source

v0.7.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.

🔕 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 enabled auto-merge (squash) December 13, 2025 17:27
@renovate renovate bot force-pushed the renovate/openmfp-eslint-config-typescript-0.x branch 3 times, most recently from 2495cd9 to 274907b Compare December 18, 2025 09:11
@renovate
Copy link
Contributor Author

renovate bot commented Dec 18, 2025

⚠️ 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.0.0" 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.11
npm error   node_modules/@openmfp/eslint-config-typescript
npm error     dev @openmfp/eslint-config-typescript@"0.7.11" 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-06T16_58_03_279Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-06T16_58_03_279Z-debug-0.log

@renovate renovate bot force-pushed the renovate/openmfp-eslint-config-typescript-0.x branch from 274907b to 70f7cf9 Compare December 23, 2025 14:08
@renovate renovate bot force-pushed the renovate/openmfp-eslint-config-typescript-0.x branch 2 times, most recently from aacef49 to d218c4a Compare January 5, 2026 21:09
@renovate renovate bot changed the title chore(deps): update dependency @openmfp/eslint-config-typescript to v0.7.8 chore(deps): update dependency @openmfp/eslint-config-typescript to v0.7.9 Jan 5, 2026
@renovate renovate bot force-pushed the renovate/openmfp-eslint-config-typescript-0.x branch 2 times, most recently from 110588f to 1c6f12a Compare January 6, 2026 14:28
@renovate renovate bot force-pushed the renovate/openmfp-eslint-config-typescript-0.x branch from 1c6f12a to 5cbd14f Compare January 6, 2026 16:58
@renovate renovate bot changed the title chore(deps): update dependency @openmfp/eslint-config-typescript to v0.7.9 chore(deps): update dependency @openmfp/eslint-config-typescript to v0.7.11 Jan 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant