Repository navigation
[release/v1.45.x-0.66bx] Declare AnyValue and AttributeValue as explicit type aliases - #5750
Merged
emdneto merged 1 commit intoOct 6, 2026
Conversation
* Declare AnyValue and AttributeValue as explicit type aliases `AnyValue = AttributeValue = ...` is a chained assignment, which type checkers don't recognize as a type alias: mypy rejects both names and pyright rejects `AnyValue`, so annotations using them fail with `valid-type` / `reportInvalidTypeForm`. Fixes #5701 Assisted-by: Claude Opus 5.5 * Add changelog fragment Assisted-by: Claude Opus 5.5
Pull request dashboard statusMerged · refreshed 2026-10-06 15:49 UTC Status above doesn't look right?
|
emdneto
approved these changes
Oct 6, 2026
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
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.
Clean cherry-pick of #5703 to the
release/v1.45.x-0.66bxbranch.