logging-objects-with-schema 0.4.0__tar.gz → 0.4.1__tar.gz

{logging_objects_with_schema-0.4.0 → logging_objects_with_schema-0.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: logging-objects-with-schema
-Version: 0.4.0
+Version: 0.4.1
 Summary: Proxy logging wrapper that validates extra fields against a JSON schema.
 Keywords: logging,schema,validation,structured-logging,structured-logs
 Author: Dmitrii Safronov
@@ -18,8 +18,8 @@ Classifier: Intended Audience :: Developers
 Classifier: Topic :: System :: Logging
 Classifier: Typing :: Typed
 Requires-Python: >=3.10
-Project-URL: Issues, https://github.com/disafronov/python-logging-objects-with-schema/issues
 Project-URL: Source, https://github.com/disafronov/python-logging-objects-with-schema
+Project-URL: Issues, https://github.com/disafronov/python-logging-objects-with-schema/issues
 Description-Content-Type: text/markdown
 
 # python-logging-objects-with-schema
@@ -365,3 +365,5 @@ All keys are merged together - they are not replaced, only supplemented.
   keys are used, maintaining 100% backward compatibility
 - `None` and empty `set()` are semantically equivalent for `forbidden_keys` -
   both mean "no additional forbidden keys" and produce the same result
+
+<!--placeholder -->

{logging_objects_with_schema-0.4.0 → logging_objects_with_schema-0.4.1}/README.md

@@ -341,3 +341,5 @@ All keys are merged together - they are not replaced, only supplemented.
   keys are used, maintaining 100% backward compatibility
 - `None` and empty `set()` are semantically equivalent for `forbidden_keys` -
   both mean "no additional forbidden keys" and produce the same result
+
+<!--placeholder -->

{logging_objects_with_schema-0.4.0 → logging_objects_with_schema-0.4.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "uv_build"
 
 [project]
 name = "logging-objects-with-schema"
-version = "0.4.0"
+version = "0.4.1"
 description = "Proxy logging wrapper that validates extra fields against a JSON schema."
 readme = "README.md"
 requires-python = ">=3.10"