From 3f554f6f8ed1e00f7b94a7062a35159985ddaa47 Mon Sep 17 00:00:00 2001 From: Vlada Dusek Date: Wed, 18 Feb 2026 09:49:41 +0100 Subject: [PATCH] fix: access model_fields from class instead of instance Fixes PydanticDeprecatedSince211 warning about accessing model_fields on an instance, which is deprecated since Pydantic V2.11. Co-Authored-By: Claude Opus 4.6 --- src/apify/_configuration.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/apify/_configuration.py b/src/apify/_configuration.py index 856c5fd0..ddf55513 100644 --- a/src/apify/_configuration.py +++ b/src/apify/_configuration.py @@ -505,7 +505,7 @@ def from_configuration(cls, configuration: CrawleeConfiguration) -> Configuratio # Due to known Pydantic issue https://github.com/pydantic/pydantic/issues/9516, creating new instance of # Configuration from existing one in situation where environment can have some fields set by alias is very # unpredictable. Use the stable workaround. - for name in configuration.model_fields: + for name in type(configuration).model_fields: setattr(apify_configuration, name, getattr(configuration, name)) return apify_configuration