Skip to content

chore(deps): lock file maintenance#33

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/lock-file-maintenance
Open

chore(deps): lock file maintenance#33
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Oct 6, 2025

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

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


Configuration

📅 Schedule: Branch creation - "before 4am on monday" in timezone Europe/Rome, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, 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 renovate Bot force-pushed the renovate/lock-file-maintenance branch from a3ba148 to d82e3d1 Compare October 21, 2025 11:15
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from d82e3d1 to 8e338cb Compare November 11, 2025 01:00
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 8e338cb to 0ea1cc3 Compare November 19, 2025 00:53
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 0ea1cc3 to 60f014a Compare December 3, 2025 14:56
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 60f014a to 9e0106c Compare December 31, 2025 16:55
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 9e0106c to 0eaa717 Compare January 8, 2026 19:46
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from eb085c7 to 846c1a5 Compare January 23, 2026 20:05
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 846c1a5 to dcfbf70 Compare February 2, 2026 17:11
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from dcfbf70 to ae9da4b Compare February 12, 2026 10:54
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Feb 17, 2026

⚠️ 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: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 47, reused 0, downloaded 0, added 0
Progress: resolved 118, reused 0, downloaded 0, added 0
Progress: resolved 234, reused 0, downloaded 0, added 0
Progress: resolved 349, reused 0, downloaded 0, added 0
Progress: resolved 491, reused 1, downloaded 0, added 0
Progress: resolved 641, reused 1, downloaded 0, added 0
Progress: resolved 792, reused 1, downloaded 0, added 0
Progress: resolved 969, reused 1, downloaded 0, added 0
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

This error happened while installing the dependencies of neostandard@0.12.2
 at typescript-eslint@8.58.1
 at @typescript-eslint/parser@8.58.1
 at @typescript-eslint/visitor-keys@8.58.1

Your Node version is incompatible with "eslint-visitor-keys@5.0.1".

Expected version: ^20.19.0 || ^22.13.0 || >=24
Got: v23.11.1

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants