Releases: Ecodev/graphql-upload
8.0.0
BREAKING CHANGE
-
Returns HTTP code 413 when
post_max_sizeis exceeded #11708This case is not directly reported by PHP itself, neither via
UploadedFileInterface, so we try our best to detect the situation and
immediately returns the HTTP code 413. We do it immediately because when
the case happens, PHP will leave $_POST entirely empty so we have no way
to do anything further. So we let the client know via HTTP status and it
is up to him to handle in the best way possible.When a 413 happens, the response body contains a detailed message
similar to:{"message": "The server `post_max_size` is configured to accept 10.00 MiB, but received 28.00 MiB"} -
UploadMiddleware::processRequest()is dropped entirely without replacement.
If you need to use this library but you don't already use PSR-15 middleware,
then you will have to implement a workaround yourself.
Added
-
Failed upload will throw the new
UploadError#11708Previously it was up to the application to validate that the received
UploadedFileInterfacewas$file->getError() === UPLOAD_ERR_OK. This
is now included inUploadTypeand allUploadedFileInterfacereceived
by the application are guaranteed to be successful uploads.
Changed
- Drop support for PHP 8.1
7.0.0
BREAKING CHANGE
- Updated to webonyx/graphql-php 15 which has some breaking changes
- Most classes are final
Added
- PHP 8.2 support
6.1.5
Changes
- Update GitHub Actions
6.1.4
Changes
- Fixes CVE-2022-31109
- Update PHP deps
6.1.3
Changes
- Minimal version is PHP 8.1
6.1.2
6.1.2
6.1.1
Changes
- Minimal version is PHP 7.4
6.1.0
Added
- PHP 8 support
6.0.0
5.0.0
Fixed
- Exclude dev files from composer package
BREAKING CHANGE
-
Remove outdated workaround for
operationNameandoperationThis is a breaking change only if you rely on the existing of
operation
instead ofoperationNamein subsequent middleware. It is not breaking
if you only useGraphQL\Server\StandardServer.