build(deps): bump python-multipart from 0.0.27 to 0.0.31 in /samples/server/petstore/python-fastapi
Bumps python-multipart from 0.0.27 to 0.0.31.
Release notes
Sourced from python-multipart's releases.
Version 0.0.31
What's Changed
- Speed up multipart header parsing and callback dispatch by
@Kludexin Kludex/python-multipart#295- Bound header field name size before validating by
@Kludexin Kludex/python-multipart#296- Validate Content-Length is non-negative in parse_form by
@Kludexin Kludex/python-multipart#297Full Changelog: https://github.com/Kludex/python-multipart/compare/0.0.30...0.0.31
Version 0.0.30
What's Changed
- Treat only
&as the urlencoded field separator by@Kludexin Kludex/python-multipart#290- Ignore RFC 2231 extended parameters in
parse_options_headerby@Kludexin Kludex/python-multipart#291Full Changelog: https://github.com/Kludex/python-multipart/compare/0.0.29...0.0.30
Version 0.0.29
What's Changed
- Handle malformed RFC 2231 continuations in
parse_options_headerby@manunioin Kludex/python-multipart#270Full Changelog: https://github.com/Kludex/python-multipart/compare/0.0.28...0.0.29
Version 0.0.28
What's Changed
- Speed up partial-boundary tail scan via
bytes.findby@Kludexin Kludex/python-multipart#281- Cap multipart boundary length at 256 bytes by
@Kludexin Kludex/python-multipart#282Full Changelog: https://github.com/Kludex/python-multipart/compare/0.0.27...0.0.28
Changelog
Sourced from python-multipart's changelog.
0.0.31 (2026-06-04)
- Speed up multipart header parsing and callback dispatch #295.
- Bound header field name size before validating #296.
- Validate
Content-Lengthis non-negative inparse_form#297.0.0.30 (2026-05-31)
- Parse
application/x-www-form-urlencodedbodies per the WHATWG URL standard, treating only&as a field separator #290.- Ignore RFC 2231/5987 extended parameters (
name*,filename*) inparse_options_header, keeping the plain parameter authoritative per RFC 7578 §4.2 #291.0.0.29 (2026-05-17)
- Handle malformed RFC 2231 continuations in
parse_options_header#270.0.0.28 (2026-05-10)
Commits
4cffc68Version 0.0.31 (#298)c814948Reject negativeContent-Lengthinparse_form(#297)6b837d4Bound header field name size before validating (#296)e0c4f9dBump the github-actions group with 3 updates (#294)b8a01bbBump the python-packages group with 3 updates (#293)6732164Speed up multipart header parsing and callback dispatch (#295)9d3ead5Version 0.0.30 (#292)3506c15Ignore RFC 2231 extended parameters inparse_options_header(#291)d69df35Treat only&as the urlencoded field separator (#290)1e6ff97Bump idna from 3.11 to 3.15 (#289)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
Summary by cubic
Upgrade python-multipart from 0.0.27 to 0.0.31 in the Python FastAPI petstore sample to improve multipart/form parsing and tighten validation. This reduces parsing overhead and aligns urlencoded parsing with the WHATWG standard.
- Dependencies
- Updated
samples/server/petstore/python-fastapi/requirements.txt. - Gains: faster header parsing and stricter checks (header name size, boundary cap, non‑negative Content-Length); urlencoded parsing uses only
&, ignores RFC 2231 extended params.
- Updated