[yeongseon]

🤖 I have created a release beep boop

0.16.0 (2026-10-26)

Features

• redaction: add optional secure logging mode (#617) (f0afe51)

Bug Fixes

• context: forward async generator send and throw operations (#599) (0e64e12), closes #585
• context: keep cold-start state stable across generator resumes (#600) (8c6d91f), closes #586
• context: make injection strategy changes safely reversible (#644) (904ec8d)
• context: preserve decorated synchronous generator return values (#598) (b7c7002), closes #584
• context: tolerate unbound extra context variables in both injection modes (#602) (a988169), closes #583
• decorator: fully resolve quoted postponed handler annotations (#597) (cdeffb3), closes #582
• decorator: honor lifecycle logging for generator handlers (#601) (f30855f), closes #587
• filters: preserve pre-existing record attributes while flattening (#605) (2d493b8), closes #280
• handlers: bound copy-budget breadth, not just container depth (#612) (2bc53d8), closes #611
• handlers: preserve LogRecord metadata when the copy budget is exhausted (#604) (80c3cb4), closes #580
• otel: recognize inherited logging handlers before assigning formatters (#603) (ae580df), closes #581
• redaction: redact sensitive keys in top-level tuple extras without patterns (#595) (0ad6de9), closes #579

---

This PR was generated with Release Please. See documentation.

[yeongseon]

Left unchanged and unmerged: this Release Please PR is the maintainer action that creates the tag/release and starts publication. No versions, changelog, manifest or tags were edited. A release would additionally require the in-chain Azure/host/runtime-audit gates and post-publication cookbook verification; that full process was not performed in this repository-only pass. Pending secure logging #617 is not part of this released scope unless it lands and Release Please regenerates the release PR.