NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist · #693 most downloaded on Packagist
Build a fully-featured hypermedia or GraphQL API in minutes!
Last release 2 days ago
29 Sep 2026
Release timing varies
gaps range from 8 days to 2 months
Nearly every release is documented
notes for 56 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
393 releases · first in 2015
774590069 fix(laravel): add contact & license options to fix swagger UI issues
Also contains v3.4.7 changes.
417fef5da fix(laravel): overlaping route format
Also contains v3.4.6 changes.
One column per quarter.
dddb97075 fix(symfony): default formats order
17c916c3a fix(symfony): BackedEnumProvider typo fix
195c4e788 fix(hydra): hydra context changed
195c4e788 fix(hydra): hydra context changed (#6710)
4f65ef2d0 fix(metadata): providing parameter constraints skips automatic ones (#6756)
5a8ef115a fix(symfony): ECMA-262 pattern with RegExp validator (#6733)
67c5a2a24 fix(laravel): jsonapi error serialization (#6755)
ac6f667f3 fix(laravel): collection relations other than HasMany (#6737)
cecd77149 feat(laravel): use laravel cache setting (#6751)
4171d5f9c fix(graphql): register query parameter arguments with filters
2e8287dad fix(laravel): allow serializer attributes through ApiProperty
025f63e69 fix(laravel): route registration of EntrypointController should be last
219199db3 fix(symfony): missing alias to serializer context builder interface
Notes:
standard_put=true is now the default, you can set it to false using extra_properties.defaults
eb80a1a56 fix(state): precise format on content-location
7c5689626 fix(laravel): call authorize on delete but not validation
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
0a461d749 fix(symfony): allow schema restriction for collection like property from choice constraint
Nothing published for this version
Nothing published for this version
Nothing published for this version
f7f9f5427 fix(laravel): phpstan/doc-parser is mandatory
Nothing published for this version
9eb5c4e94 fix(symfony): suggest DocumentationAction as replacement for deprecated SwaggerUiAction
ab03b5544 fix(openapi): typing issue with openapiContext in #[ApiProperty]
openapiContext in #[ApiProperty] (#6910)2b3c55db2 fix(symfony): remove unsolvable deprecation (#6899) see also
I mispublished a v3.4.13 on some repositories to fix them all I bumped 3.4.10 to 3.4.14 More details at #6888.
Nothing published for this version
2ee5eb496 fix(symfony): mercure exception formatting by calling array_keys()
a209dd440 fix: add missing error normalizer trait and remove deprecated interface
Parameter::getValue() now takes a default value as argument getValue(mixed $default = new ParameterNotFound()): mixedParametes::get(string $key, string $parameterClass = QueryParameter::class) (but also has and remove) now has a default value as second argument to QueryParameter::classproperty, fixed by using the key instead86c97cac3 fix(symfony): symfony 7.2 deprecations
2d25e79e0 fix(symfony): unset item_uri_template when serializing an error
17c916c3a fix(symfony): service typo fix BackedEnumProvider for autowiring
fc8fa00a1 fix(hydra): iri template when using query parameter
550347867 fix(graphql): register query parameter arguments with filters
3ca599158 fix(hydra): hydra_prefix on errors
0ca76fc89 fix(elasticsearch): allow elasticsearch 7
219199db3 fix(symfony): missing alias to serializer context builder interface
Namespaces like ApiPlatform/Api or ApiPlatform/Util are deprecated and will be removed in 4.0. You should now install api-platform/symfony instead of…
Namespaces like ApiPlatform/Api or ApiPlatform/Util are deprecated and will be removed in 4.0.
You should now install api-platform/symfony instead of api-platform/core.
Read the upgrade guide for detailed steps.
Various fixes for components isolation.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Namespaces like ApiPlatform/Api or ApiPlatform/Util are deprecated and will be removed in 4.0. You should now install api-platform/symfony instead of…
Namespaces like ApiPlatform/Api or ApiPlatform/Util are deprecated and will be removed in 4.0.
You should now install api-platform/symfony instead of api-platform/core.
Various fixes for components isolation.
Namespaces like ApiPlatform/Api or ApiPlatform/Util are deprecated and will be removed in 4.0. You should now install api-platform/symfony instead of…
Namespaces like ApiPlatform/Api or ApiPlatform/Util are deprecated and will be removed in 4.0.
You should now install api-platform/symfony instead of api-platform/core.
Nothing published for this version
Namespaces like ApiPlatform/Api or ApiPlatform/Util are deprecated and will be removed in 4.0. You should now install api-platform/symfony instead of…
Namespaces like ApiPlatform/Api or ApiPlatform/Util are deprecated and will be removed in 4.0.
You should now install api-platform/symfony instead of api-platform/core.
26d5cbb9b feat: deprecate query parameter validator
9eb5c4e94 fix(symfony): suggest DocumentationAction as replacement for deprecated SwaggerUiAction
4c58b33e8 fix(jsonapi): fixed definition name to allow using the same class names in different namespaces
1b9dfccc8 fix: count TraversablePaginator
0e91b0451 fix: use correct class in FilterValidationException deprecation message
344b8b245 Revert "feat(jsonschema): make JSON-LD specific properties required (#6366)"
6776231ed fix: remove useless deprecation
84df46786 fix(jsonld): remove request uri variables when denormalizing output
0edc73806 fix(state): allow to skip parameter validator provider
These are enhancement to the experimental Parameter feature:
0ed1b637a fix(metadata): wrong schema generated if openapicontext set on array
8e253d4d7 fix(graphql): validate after resolver
Notes:
The patch at #6426 introduces a new validateAfterResolver option to mitigate the BC-break introduced in 3.3 that does the validation before calling the resolver:
new Mutation(
resolver: 'app.graphql.mutation_resolver.activity_log',
name: 'create',
validateAfterResolver: true,
validate: false
)
55f27dc7a fix(symfony): documentation request _format
002d8e514 fix(validation): ValidationException causes TypeError exception when called with $code=null
10f24f7a1 fix(state): no location header without output
6f806f4ee fix(state): read without output
You can remove the event_listeners_backward_compatibility_layer flag and set use_symfony_listeners instead. The use_symfony_listeners should be true if you use controllers or if you rely on Symfony event listeners. Note that now flags like read can be forced to true if you want to call a Provider even on POST operations. These are the rules we set up on runtime if no value has been set:
if (null === $operation->canValidate()) {
$operation = $operation->withValidate(!$request->isMethodSafe() && !$request->isMethod('DELETE'));
}
if (null === $operation->canRead()) {
$operation = $operation->withRead($operation->getUriVariables() || $request->isMethodSafe());
}
if (null === $operation->canDeserialize()) {
$operation = $operation->withDeserialize(\in_array($operation->getMethod(), ['POST', 'PUT', 'PATCH'], true));
}
Previously listeners did the checks before reading our flags and you could not force the values.
When using GraphQl, with event_listeners_backward_compatibility_layer: true, mutation resolver gets called before validation, when using false (the future default) validation occurs on the user's input.
6f806f4ee fix(state): read without output
629da787b fix(symfony): use non deprecated validator exception
Your coding agent can read these notes before it upgrades. Set up the MCP server →