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 #164

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

titouanmathis
Copy link
Collaborator

@titouanmathis titouanmathis commented Jun 24, 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 - "* 0-3 * * 1" (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

This PR has been generated by Renovate Bot.

@titouanmathis
Copy link
Collaborator Author

titouanmathis commented Jun 24, 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 warn ERESOLVE overriding peer dependency
npm warn While resolving: @studiometa/[email protected]
npm warn Found: [email protected]
npm warn node_modules/tailwindcss
npm warn   peer tailwindcss@"1 || 2 || 2.0.1-compat || 3" from [email protected]
npm warn   node_modules/tailwind-config-viewer
npm warn     tailwind-config-viewer@"^2.0.4" from @studiometa/[email protected]
npm warn     packages/webpack-config
npm warn
npm warn Could not resolve dependency:
npm warn peer tailwindcss@"1 || 2 || 2.0.1-compat || 3" from [email protected]
npm warn node_modules/tailwind-config-viewer
npm warn   tailwind-config-viewer@"^2.0.4" from @studiometa/[email protected]
npm warn   packages/webpack-config
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @studiometa/[email protected]
npm error Found: [email protected]
npm error node_modules/remark
npm error   remark@"^15.0.1" from @studiometa/[email protected]
npm error   packages/preset-markdown
npm error     @studiometa/[email protected]
npm error     node_modules/@studiometa/webpack-config-preset-markdown
npm error       workspace packages/preset-markdown from the root project
npm error       1 more (@studiometa/webpack-config-preset-prototyping)
npm error
npm error Could not resolve dependency:
npm error peer remark@"^14.0.0" from [email protected]
npm error node_modules/remark-loader
npm error   remark-loader@"^6.0.0" from @studiometa/[email protected]
npm error   packages/preset-markdown
npm error     @studiometa/[email protected]
npm error     node_modules/@studiometa/webpack-config-preset-markdown
npm error       workspace packages/preset-markdown from the root project
npm error       1 more (@studiometa/webpack-config-preset-prototyping)
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-12-10T13_57_52_914Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-10T13_57_52_914Z-debug-0.log

@titouanmathis titouanmathis force-pushed the renovate/lock-file-maintenance branch from 0f10e4e to bfc8fa1 Compare July 4, 2024 13:53
@titouanmathis titouanmathis force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 5e086ce to b8340fa Compare July 24, 2024 12:58
@titouanmathis titouanmathis force-pushed the renovate/lock-file-maintenance branch 6 times, most recently from f311de0 to a2c2c73 Compare November 11, 2024 13:05
@titouanmathis titouanmathis changed the title Lock file maintenance chore(deps): lock file maintenance Nov 22, 2024
@titouanmathis titouanmathis force-pushed the renovate/lock-file-maintenance branch from a2c2c73 to e2cfe34 Compare November 22, 2024 17:56
@titouanmathis titouanmathis force-pushed the renovate/lock-file-maintenance branch from e2cfe34 to ccfe2a2 Compare December 10, 2024 13:58
@titouanmathis titouanmathis changed the title chore(deps): lock file maintenance Lock file maintenance Dec 10, 2024
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.

2 participants