Skip to content
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

Lock file maintenance #371

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 11, 2023

Mend Renovate

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 UTC, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the maintenance label Sep 11, 2023
@renovate renovate bot enabled auto-merge (squash) September 11, 2023 02:01
@renovate renovate bot force-pushed the renovate/lockfile-maintenance branch from 6a4859a to 1e9f8e0 Compare October 9, 2023 08:02
@renovate renovate bot force-pushed the renovate/lockfile-maintenance branch from 1e9f8e0 to 26611c0 Compare October 24, 2023 04:26
@renovate renovate bot force-pushed the renovate/lockfile-maintenance branch 2 times, most recently from f2d481a to ea0b4b9 Compare November 1, 2023 19:20
@renovate renovate bot force-pushed the renovate/lockfile-maintenance branch from ea0b4b9 to 0664473 Compare December 1, 2023 03:24
@renovate renovate bot force-pushed the renovate/lockfile-maintenance branch from 0664473 to 1c9c17f Compare January 1, 2024 04:18
@renovate renovate bot force-pushed the renovate/lockfile-maintenance branch from 1c9c17f to 57f15ac Compare January 18, 2024 04:55
@renovate renovate bot force-pushed the renovate/lockfile-maintenance branch from 57f15ac to 1715170 Compare February 5, 2024 04:36
@renovate renovate bot force-pushed the renovate/lockfile-maintenance branch from 1715170 to ae97e94 Compare March 1, 2024 03:41
@renovate renovate bot force-pushed the renovate/lockfile-maintenance branch from ae97e94 to 5f915ab Compare April 29, 2024 05:06
Copy link
Contributor Author

renovate bot commented May 1, 2024

⚠ 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: @croct/[email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"^9.0.0" from the root project
npm error   peer eslint@">= 8" from @croct/[email protected]
npm error   node_modules/@croct/eslint-plugin
npm error     dev @croct/eslint-plugin@"^0.7.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/parser
npm error   peer @typescript-eslint/parser@">= 6" from @croct/[email protected]
npm error   node_modules/@croct/eslint-plugin
npm error     dev @croct/eslint-plugin@"^0.7.0" 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 /tmp/renovate/cache/others/npm/_logs/2024-05-05T21_05_42_970Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-05T21_05_42_970Z-debug-0.log

auto-merge was automatically disabled May 5, 2024 21:13

Pull request was closed

@marcospassos marcospassos deleted the renovate/lockfile-maintenance branch May 5, 2024 21:13
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.

2 participants