Skip to content

Lock file maintenance #328

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 1.29.x
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 11, 2024

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 - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone UTC, 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

Read more information about the use of Renovate Bot within Laminas.

@renovate renovate bot added the renovate label Dec 11, 2024
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from ce7cc3a to 27486c4 Compare January 17, 2025 11:14
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 27486c4 to 657d508 Compare January 17, 2025 11:36
Copy link
Contributor Author

renovate bot commented Mar 2, 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: laminas-ci-matrix-action@undefined
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"^8.26.0" from the root project
npm error   peer eslint@">= 7" from [email protected]
npm error   node_modules/eslint-config-incredible
npm error     dev eslint-config-incredible@"^2.4.2" from the root project
npm error   2 more (eslint-plugin-import, eslint-plugin-markdown)
npm error
npm error Could not resolve dependency:
npm error peer eslint@">=9.0.0" from [email protected]
npm error node_modules/eslint-plugin-mocha
npm error   peer eslint-plugin-mocha@">= 8" from [email protected]
npm error   node_modules/eslint-config-incredible
npm error     dev eslint-config-incredible@"^2.4.2" 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-08-15T02_28_43_763Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-08-15T02_28_43_763Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants