chore(release): prepare v0.13.0#56
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR performs a release version bump for the ChangesRelease 0.13.0
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Documentation
multipartkit/infer.content_type_from_filenameandcontent_type_from_bytesdocstrings, and the README "Pluggable content-type inference" bullet, now state explicitly that these top-level helpers are default no-ops of the pluggable inference interface and always returnNone; callers wanting real inference must wire anInferer(e.g. backed bynao1215/mimetype) intoform.add_file_auto_with. (infer.content_type_from_filename/from_bytes are no-op defaults — silently return None for known types #52)Added
multipartkit/form.add_field_strictandadd_file_strictnow reject empty or whitespace-onlynamewith the newError(EmptyFieldName(value:))variant, aligning with RFC 7578 §4.2 which requires theContent-Dispositionnameparameter to be the field name; the non-strictadd_field/add_filekeep their existing silent-accept behaviour for backward compatibility. (form.add_field accepts empty name silently — RFC 7578 §4.2 says name MUST be field name #51)Changed
multipartkit/content_disposition.parsenow enforces RFC 7230 §3.2.6quoted-pairstrictly: a\XwhoseXis outsideHTAB / SP / VCHAR / obs-text(for exampleNUL,CR,LF, or any other ASCII control byte) is rejected with the newError(InvalidQuotedPair(_))instead of silently dropping the backslash, blockingNUL-smuggling into the decodedname/filename. (content_disposition.parse over-eager quoted-pair unescape — drops backslash before non-VCHAR (NUL, CR, LF) silently #50)Summary by CodeRabbit
Release 0.13.0 (2026-05-20)
New Features
Bug Fixes