chore: update pylance dependency to v9.0.0b9#5211
Open
lance-community wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pylancedependency requirement topylance>=9.0.0b9.pylanceto the triggering Lance tag because9.0.0b9is not yet available from the configured package indexes.uv.lock, including the compatiblelance-namespacedependency updates required by the tagged Pylance metadata.make lintto pass.Verification
protobuf-compileron the runner to satisfy the git-sourced Pylance build prerequisite.make lockmake lintTriggering tag: refs/tags/v9.0.0-beta.9