Skip to content

chore(deps): lock file maintenance#955

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

chore(deps): lock file maintenance#955
renovate[bot] wants to merge 1 commit intomainfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 1, 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 America/Santiago, 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 1, 2024
@renovate renovate bot requested a review from gperdomor as a code owner February 1, 2024 04:24
@nx-cloud
Copy link

nx-cloud bot commented Feb 1, 2024

View your CI Pipeline Execution ↗ for commit 5ef21f8

Command Status Duration Result
nx affected -t lint test build typecheck e2e-ci ✅ Succeeded 1m 41s View ↗
nx-cloud record -- pnpm exec nx format:check ✅ Succeeded 4s View ↗

☁️ Nx Cloud last updated this comment at 2026-02-28 04:06:00 UTC

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from a399b1b to 5209dd1 Compare February 17, 2024 01:51
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 5209dd1 to 451698f Compare March 30, 2024 23:06
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 7 times, most recently from 3a9905a to 4decf62 Compare April 15, 2024 19:24
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 976729c to ebd2f15 Compare May 31, 2024 17:27
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from ebd2f15 to f7479af Compare June 4, 2024 15:20
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 232789d to 3231b85 Compare July 13, 2024 00:25
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 7 times, most recently from f54e2b8 to 533a16b Compare August 9, 2024 02:54
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 7fac9ef to 64f9a21 Compare October 3, 2024 01:56
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 46a3920 to c6671f3 Compare December 10, 2024 00:43
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from b6432b2 to 097b56d Compare May 19, 2025 20:11
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 097b56d to 94d60a0 Compare June 11, 2025 04:19
@vercel
Copy link
Contributor

vercel bot commented Jun 11, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
cvb Ready Ready Preview, Comment Feb 28, 2026 4:55am
nx-tools Ready Ready Preview, Comment Feb 28, 2026 4:55am

@vercel
Copy link
Contributor

vercel bot commented Oct 14, 2025

Deployment failed with the following error:

Resource is limited - try again in 1 hour (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/gustavo-perdomos-projects?upgradeToPro=build-rate-limit

@vercel
Copy link
Contributor

vercel bot commented Oct 14, 2025

Deployment failed with the following error:

Resource is limited - try again in 56 minutes (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/gustavo-perdomos-projects?upgradeToPro=build-rate-limit

@vercel
Copy link
Contributor

vercel bot commented Oct 14, 2025

Deployment failed with the following error:

Resource is limited - try again in 53 minutes (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/gustavo-perdomos-projects?upgradeToPro=build-rate-limit

@vercel
Copy link
Contributor

vercel bot commented Oct 14, 2025

Deployment failed with the following error:

Resource is limited - try again in 51 minutes (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/gustavo-perdomos-projects?upgradeToPro=build-rate-limit

@vercel
Copy link
Contributor

vercel bot commented Oct 14, 2025

Deployment failed with the following error:

Resource is limited - try again in 41 minutes (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/gustavo-perdomos-projects?upgradeToPro=build-rate-limit

@vercel
Copy link
Contributor

vercel bot commented Oct 14, 2025

Deployment failed with the following error:

Resource is limited - try again in 3 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/gustavo-perdomos-projects?upgradeToPro=build-rate-limit

@vercel
Copy link
Contributor

vercel bot commented Oct 14, 2025

Deployment failed with the following error:

Resource is limited - try again in 2 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/gustavo-perdomos-projects?upgradeToPro=build-rate-limit

Copy link

@nx-cloud nx-cloud bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.

Nx Cloud has identified a possible root cause for your failed CI:

Our analysis determined this is an environment_state issue rather than a code_change because the identical TypeScript compilation error (nx@22.5.0 vs nx@22.5.1 type incompatibilities) already exists in the main branch, and this PR contains zero code modifications—only lock file maintenance. The workspace has a pre-existing dependency resolution issue with dual Nx versions that requires infrastructure-level remediation.

No code changes were suggested for this issue.

Trigger a rerun:

Rerun CI

Nx Cloud View detailed reasoning on Nx Cloud ↗


🎓 Learn more about Self-Healing CI on nx.dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant