Skip to content

Lock file maintenance#2710

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/lock-file-maintenance
Open

Lock file maintenance#2710
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Nov 17, 2025

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 US/Eastern)

  • 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 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 16 times, most recently from e59492f to 9a748c7 Compare November 24, 2025 15:14
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from b661f12 to 730eaf2 Compare November 30, 2025 16:18
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 11 times, most recently from 1fc4b54 to 3be6b7c Compare December 12, 2025 17:37
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from 8be9d5f to 82f5490 Compare December 22, 2025 21:18
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 9 times, most recently from 5ed8e78 to aa167b2 Compare January 6, 2026 16:46
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 11 times, most recently from c7e1540 to d555938 Compare January 13, 2026 15:34
Comment thread uv.lock Outdated
[[package]]
name = "grpcio"
version = "1.78.1"
version = "1.78.0"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: Downgrading grpcio to 1.78.0 reintroduces a fork support bug that could cause intermittent failures in the gRPC-based vector search feature in multithreaded environments.
Severity: MEDIUM

Suggested Fix

Investigate the dependency constraints forcing the downgrade of grpcio to 1.78.0. If the downgrade is not intentional or required, override the dependency to ensure grpcio remains at version 1.78.1 or newer to avoid the known fork support bug.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: uv.lock#L1510

Potential issue: The `grpcio` package is being downgraded from version 1.78.1 to 1.78.0.
Version 1.78.0 has a known bug related to fork support in multithreaded environments,
which was fixed in 1.78.1. The application uses `grpcio` for its vector search feature
via the `qdrant-client` with `prefer_grpc=True`, and it operates in a
multithreaded/asynchronous context using Celery and Django. This downgrade introduces a
risk of intermittent failures in the vector search functionality if the specific
conditions that trigger the bug are met during execution.

Did we get this right? 👍 / 👎 to inform future reviews.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 15, 2026

OpenAPI Changes

No changes detected

View full changelog

Unexpected changes? Ensure your branch is up-to-date with main (consider rebasing).

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 5, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant