Skip to content

Lock file maintenance - #34

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

Lock file maintenance#34
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Apr 13, 2026

Copy link
Copy Markdown
Contributor

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: (in timezone America/Los_Angeles)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • 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.

👻 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.

@pkg-pr-new

pkg-pr-new Bot commented Apr 13, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@convex-dev/twilio@34

commit: aa34fee

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 3784899 to 71fdd78 Compare April 21, 2026 00:58
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from d75050a to bed966f Compare May 4, 2026 14:03
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 95f4f94 to 7c556d3 Compare May 14, 2026 21:47
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 6dbe136 to 8a44dbf Compare May 21, 2026 21:29
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 05b1d6d to 4bd1a32 Compare June 1, 2026 20:53
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 2c053cf to 63a854c Compare June 16, 2026 00:04
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from e665229 to bfdbd75 Compare July 17, 2026 09:53
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from c80af1c to 2e80bd3 Compare July 24, 2026 21:01
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 2e80bd3 to aa34fee Compare July 30, 2026 19:53
@renovate

renovate Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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: @convex-dev/twilio@0.2.2
npm error Found: convex@1.42.3
npm error node_modules/convex
npm error   dev convex@"1.42.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer convex@"^1.43.0" from convex-helpers@0.1.123
npm error node_modules/convex-helpers
npm error   convex-helpers@"^0.1.106" 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/2026-08-14T20_00_34_134Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-14T20_00_34_134Z-debug-0.log

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