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

Update dependency remix-utils to v8 #1931

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 15, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
remix-utils 7.7.0 -> 8.1.0 age adoption passing confidence

Release Notes

sergiodxa/remix-utils (remix-utils)

v8.1.0

Compare Source

What's Changed

New Features
Documentation Changes
Bug Fixes

New Contributors

Full Changelog: sergiodxa/remix-utils@v8.0.0...v8.1.0

v8.0.0

Compare Source

What's Changed

New Features

New Contributors

Full Changelog: sergiodxa/remix-utils@v7.7.0...v8.0.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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.

Copy link
Contributor Author

renovate bot commented Dec 15, 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 could not resolve
npm error
npm error While resolving: festival@undefined
npm error Found: [email protected]
npm error node_modules/react-router
npm error   peer react-router@"^6.0.0" from @clerk/[email protected]
npm error   node_modules/@clerk/remix
npm error     @clerk/remix@"4.5.0" from the root project
npm error   react-router@"6.29.0" from @remix-run/[email protected]
npm error   node_modules/@remix-run/react
npm error     @remix-run/react@"2.15.3" from the root project
npm error     peer @remix-run/react@"^2.0.0" from @clerk/[email protected]
npm error     node_modules/@clerk/remix
npm error       @clerk/remix@"4.5.0" from the root project
npm error     3 more (@remix-run/dev, @remix-run/testing, remix-validated-form)
npm error   1 more (react-router-dom)
npm error
npm error Could not resolve dependency:
npm error remix-utils@"8.1.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react-router
npm error   peerOptional react-router@"^7.0.0" from [email protected]
npm error   node_modules/remix-utils
npm error     remix-utils@"8.1.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 /runner/cache/others/npm/_logs/2025-02-23T03_27_54_511Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-02-23T03_27_54_511Z-debug-0.log

@renovate renovate bot force-pushed the renovate/remix-utils-8.x branch from fa95ff3 to afd3cd4 Compare January 21, 2025 00:42
@renovate renovate bot force-pushed the renovate/remix-utils-8.x branch from afd3cd4 to 77c0637 Compare February 23, 2025 03:27
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