From 9042562c546484ec4df696b4c18dcb89c08ff19e Mon Sep 17 00:00:00 2001 From: Nanaloveyuki Date: Sun, 14 Jun 2026 03:50:23 +0800 Subject: [PATCH] :bookmark: prepare 0.5.3 release notes --- docs/changes/0.5.3.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 docs/changes/0.5.3.md diff --git a/docs/changes/0.5.3.md b/docs/changes/0.5.3.md new file mode 100644 index 0000000..89c4a59 --- /dev/null +++ b/docs/changes/0.5.3.md @@ -0,0 +1,25 @@ +## BitLogger Update Changes + +version 0.5.3 + +### Docs + +- docs: expand `docs/api` coverage for sync and async facade aliases, builders, config models, state models, and runtime/file helper surfaces +- docs: clarify facade layering for `ConfiguredLogger`, `ApplicationLogger`, `LibraryLogger`, `ApplicationAsyncLogger`, `ApplicationTextAsyncLogger`, and the library async/text facades +- docs: refresh sync and async target-verification notes so published support claims stay aligned with the current validation matrix + +### Test + +- test: cover sync facade composition and parse/build contracts for configured, application, and library logger paths +- test: cover async facade helper-surface and unwrap contracts for application, library, parsed, and text-console builder paths +- test: keep sync and async package lines validated across `native`, `js`, and `wasm-gc` after the facade contract sweep + +### Runtime + +- fix: correct closed async backlog accounting so pending and dropped counts remain consistent after close and shutdown paths +- fix: hide internal file backend wrapper details from the public surface while preserving runtime file-helper behavior + +### Notes + +- this release is a contract-locking follow-up focused on making the published API reference match the live facade behavior more directly +- facade-oriented sync and async entry paths now have stronger direct tests for alias-preserved helpers, narrowing boundaries, and unwrap recovery behavior