Skip to content

chore(deps): lock file maintenance - #751

Open
mend-for-github-com[bot] wants to merge 1 commit into
mainfrom
whitesource-remediate/lock-file-maintenance
Open

chore(deps): lock file maintenance#751
mend-for-github-com[bot] wants to merge 1 commit into
mainfrom
whitesource-remediate/lock-file-maintenance

Conversation

@mend-for-github-com

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: (UTC)

  • Branch creation
    • "before 4am on monday"
  • 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

@changeset-bot

changeset-bot Bot commented Aug 10, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 70f9b5d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@nx-cloud

nx-cloud Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

View your CI Pipeline Execution ↗ for commit 70f9b5d

Command Status Duration Result
nx affected -t build lint test typecheck e2e-ci ❌ Failed 3m 16s View ↗

💡 Dealing with memory or CPU issues? See memory and CPU details with the resource usage add-on ↗.


☁️ Nx Cloud last updated this comment at 2026-08-12 16:35:22 UTC

@mend-for-github-com
mend-for-github-com Bot force-pushed the whitesource-remediate/lock-file-maintenance branch 3 times, most recently from be3b7be to c0b1a90 Compare August 10, 2026 22:25
nx-cloud[bot]

This comment was marked as outdated.

@mend-for-github-com
mend-for-github-com Bot force-pushed the whitesource-remediate/lock-file-maintenance branch 2 times, most recently from a74d7e0 to bbd87f6 Compare August 11, 2026 15:32
nx-cloud[bot]

This comment was marked as outdated.

@nx-cloud nx-cloud Bot left a comment

Copy link
Copy Markdown
Contributor

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 is proposing a fix for your failed CI:

We updated source files to resolve failures introduced by the lock file maintenance update. The new prettier version reformats union types differently (inline vs multi-line), so we ran prettier --write on all affected files across davinci-client and journey-client. Additionally, the updated immer@11.1.16 causes a TS4023 error on the exported nodeSlice because TypeScript cannot serialize WritableNonArrayDraft into declaration files; removing the redundant return newState statements from reducers (the draft is mutated in-place anyway) changes their inferred return type to void, eliminating the error.

Note

We are verifying this fix by re-running a subset of the 4 failed tasks that were analyzed.

Warning

The suggested diff is too large to display here, but you can view it on Nx Cloud ↗


Apply fix via Nx Cloud  Reject fix via Nx Cloud


Or Apply changes locally with:

npx nx-cloud apply-locally dkTu-MqJM

Apply fix locally with your editor ↗   View interactive diff ↗



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

@mend-for-github-com
mend-for-github-com Bot force-pushed the whitesource-remediate/lock-file-maintenance branch from bbd87f6 to 70f9b5d Compare August 12, 2026 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

0 participants