Release PR for 2025-12-09 09:39#35
Merged
Merged
Conversation
…ogger - Enhanced the SchemaLogger to accept an optional `forbidden_keys` parameter during initialization, allowing subclasses to specify additional forbidden root keys for schema validation. - Updated the caching mechanism in `_compile_schema_internal` to include forbidden keys in the cache key, ensuring separate caching for different sets of forbidden keys. - Modified the `_check_root_conflicts` function to merge additional forbidden keys with the built-in LogRecord attributes, maintaining backward compatibility. - Added comprehensive tests to validate the new functionality, including checks for inheritance and merging of forbidden keys. This change improves flexibility in schema validation and enhances the usability of the logging framework. Signed-off-by: Dmitrii Safronov <zimniy@cyberbrain.cc>
- Updated the README and comments in schema_loader.py and schema_logger.py to clarify that `None` and empty `set()` are semantically equivalent for the `forbidden_keys` parameter, both indicating "no additional forbidden keys." - Enhanced documentation to ensure consistency and understanding of the behavior in schema validation and caching mechanisms. This change improves clarity for developers regarding the usage of forbidden_keys in the logging framework. Signed-off-by: Dmitrii Safronov <zimniy@cyberbrain.cc>
- Updated tests for SchemaLogger to validate behavior with different configurations of the `forbidden_keys` parameter, including `None`, empty set, and non-empty sets. - Added tests to ensure correct initialization and schema handling in various scenarios, improving coverage and reliability of the logging framework. - Utilized `monkeypatch` to manage temporary directory changes during tests, ensuring isolation and consistency. This change enhances the robustness of the SchemaLogger tests and clarifies the expected behavior of the `forbidden_keys` parameter. Signed-off-by: Dmitrii Safronov <zimniy@cyberbrain.cc>
## [0.2.0-rc.1](v0.1.4...v0.2.0-rc.1) (2025-12-09) ### Features * **schema_logger:** add support for custom forbidden keys in SchemaLogger ([1d678f5](1d678f5)) Signed-off-by: Release Bot <noreply@github.com>
Modified the release message format in .releaserc.cjs to use a specific email for the semantic-release-bot, ensuring consistent attribution in release notes. Signed-off-by: Dmitrii Safronov <zimniy@cyberbrain.cc>
github-actions
Bot
changed the title
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
2 participants
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.
Changelog (#35)
✨ New Features
📚 Documentation
🧪 Tests
🧹 Chores