·
1 commit
to main
since this release
Config values True, False, and None (Python-style capitalised literals)
were silently kept as strings rather than being converted to their Python
types. This went unnoticed in older releases because pydantic v1's
parse_obj coerced the strings during validation. With the new built-in
type checker (which correctly requires actual bools), configs using the
capitalised forms broke.
Handle True/False/None in try_load_json as aliases for the JSON-style
true/false/null, and add regression tests covering both forms plus
quoted strings that must stay as strings.