Bump multipart from 1.2.1 to 1.3.0

[dependabot]

Bumps multipart from 1.2.1 to 1.3.0.

Release notes

Sourced from multipart's releases.

v1.3.0

Full Changelog: defnull/multipart@v1.2.0...v1.3.0

Changelog

Sourced from multipart's changelog.

========= Changelog

This project follows Semantic Versioning (major.minor.patch), with the exception that behavior changes are allowed in minor releases as long as the change corrects behavior to match documentation, specification or expectation. In other words: Bugfixes do not count as backward incompatible changes, even if they technically change behavior from incorrect to correct and may break applications that rely on incorrect or undefined behavior or undocumented APIs.

Release 1.4

Not released yet

• feat: More strict (and also faster) header validation within segments.
• feat: :class:PushMultipartParser is now easier to sub-class to support alternative multipart types (e.g. multipart/byterange).
• change: :attr:`MultipartSegment.name`` is now typed as optional, but is still guaranteed to be a string for unmodified versions of the parser.

Release 1.3

This release adds new APIs and contains internal or non-breaking api changes.

• feat: New convenience methods :meth:PushMultipartParser.parse_blocking and :meth:PushMultipartParser.parse_async.
• feat: Nicer error messages when reading from a closed MultipartPart.
• feat: Improved typing.
• change: segment is now a required constructor argument for MultipartPart and changed position. The constructor is not part of the public API, so this should not break user code.
• fix/change: Closing a MultipartPart should set its file to None, not False.

Release 1.2

This release improves error handling, documentation and performance, fixes several parser edge-cases and adds new functionality. API changes are backwards compatible.

• feat: Split up MultipartError into more specific exceptions and add HTTP status code hints. All exceptions are subclasses of MultipartError.
• feat: New parse_form_data(ignore_errors) parameter to throw exceptions in non-strict mode, or suppress exceptions in strict mode. Default behavior does not change (throw in strict-mode, ignore in non-strict mode).

... (truncated)

Commits

• c43c0d5 Release of 1.3.0
• f21d64b docs: Finalizing changelog
• 73738db build: Add Python 3.13 to tests
• 97358bf build: Use tox-uv for local tests
• da4ed8b Cleanup .gitignore
• 40fe6c1 feat: New convenience parser functions for blocking or async data sources.
• b1eb619 refactor: Spelling
• 4b07df4 format: Code format using black with default settings
• a16d0ee refactor: Simpler first boundary check
• b9e225e docs: 2024->2025
• 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)