fix: avoid scheduler descriptor side effects (v26.09.11) - #175
Merged
Merged
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
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
Scanning a Pydantic settings bean in
TaskScheduler.discover()evaluated deprecated instance descriptors and emitted twoPydanticDeprecatedSince211warnings in the published 26.9.10 wheel. The scheduler now uses the existing application-context descriptor guard before binding methods, without warning suppression. Ordinary, inherited, static and class scheduled methods remain discoverable and executable.This patch adds two regressions, documents the discovery contract, and updates release metadata to v26.09.11 (package 26.9.11). It introduces no public API or configuration changes.
Type of Change
Test Plan