Releases
Keep up with regular Scramble releases.
Latest versions:
Scramble: v0.13.26
Scramble PRO: v0.9.3
June 2026
Jun 2, 2026
v0.13.26
What’s Changed
- Fix missing
Referencetype during parameters serialization by @romalytvynenko in #1177
Jun 2, 2026
v0.9.3 PRO
What’s Changed
- Fix Laravel Data property being rendered as a other type when one property input name (
#[MapInputName]) and other property name collides (enum case)
May 2026
May 29, 2026
v0.13.24
What’s Changed
- Improve inference:
__support, facades support, array destructuring support by @romalytvynenko in #1167 and #1172 - Add
include/excludefiltering toscramble.api_pathby @romalytvynenko in #1168 - Automatically document API authentication by @romalytvynenko in #1170
- Improve inference by dropping type of calls to non-existing methods in unions in #1171
- Added
newCollectionsupport on models by @romalytvynenko in #1171 - Add
Responsablesupport by @romalytvynenko in #1173
May 20, 2026
v0.9.2 PRO
What’s Changed
- Fix request media type for Laravel Data objects with file properties
- Fixed compatibility with Laravel Data 4.23 by @romalytvynenko in #104
May 19, 2026
v0.13.23
What’s Changed
- Support real-time Facades by @jcsoriano in #1146
- Support type inference for method calls and property access on union types by @romalytvynenko in #1151
- Improve null coalescing operator inference by @romalytvynenko in #1152
- Improve performance for projects with many inline types by @romalytvynenko in #1163
New Contributors
- @jcsoriano made their first contribution in #1146
April 2026
Apr 27, 2026
v0.9.1 PRO
What’s Changed
- Bump Scramble to 0.13.22
Apr 27, 2026
v0.13.22
What’s Changed
- Support custom field for confirmed rule by @cappuc in #1128
- Add support for
$thisin rule expressions and improve rules evaluation safety by @romalytvynenko in #1145
Security: addresses a potential code execution issue under specific conditions.
New Contributors
- @cappuc made their first contribution in #1128
Apr 26, 2026
v0.9.0 PRO
Changes to the generated query parameters JSON schema
Parameter handling is aligned with JSON:API serialization rules and expressed using proper OpenAPI schema. Instead of documenting parameters like include as string with described values, they are now defined as arrays with enumerated items. With explode: false, these arrays are serialized as comma-separated values (e.g. include=foo,bar) while remaining arrays in the schema.
{
"name": "fields[appointments]",
"in": "query",
"schema": {
"type": "array",
"items": {
"type": "string",
"enum": [
"title",
"description",
"status",
"created_at"
]
}
},
"explode": false
}
Fallback to previous behavior is available via configuration. If you prefer the old approach where JSON:API array parameters are documented as string, you can switch the serialization strategy:
use Dedoc\Scramble\Scramble;
use Dedoc\Scramble\Enums\JsonApiArraySerialization;
Scramble::configure()
->jsonApi(
arraySerialization: JsonApiArraySerialization::String,
);
What’s changed
- Improved type inference for query builder instances. The model type is now inferred for the query builder generic, allowing Scramble to correctly document types from expressions like
QueryBuilder::from(SomeModel::class)->get()->toResourceCollection(). - When documenting Query Builder parameters, Scramble now respects the
jsonApiarraySerializationconfiguration when handling query array enum parameters (such asinclude,fields[*],sort), documenting them as arrays of specific enum values instead of listing available values in the description. - Added compatibility with Laravel’s native JSON:API implementation: Query Builder parameters take precedence when present.
- When
allowedFieldsis used, Scramble documents the fields query parameter asfields[${model table name here}]instead offields, better aligning with the JSON:API specification. - Improved relationship include documentation for
AllowedInclude::relationship(...)in Laravel Query Builder 7.0+: Scramble no longer documents redundant include values likepostsCountandpostsExistswhen onlypostsshould be available.
Apr 26, 2026
v0.13.21
What’s Changed
- Fix relationship resource guessing when not explicitly provided and recognize JSON:API parameters when resource is transformed to response by @romalytvynenko in #1143
Apr 16, 2026
v0.13.20
What’s Changed
- Add
toResourceCollectionsupport on paginators by @romalytvynenko in #1142
Apr 16, 2026
v0.13.19
What’s Changed
- Add JSON:API resources support by @romalytvynenko in #1136
- Add model’s
toResourceandtoResourceCollectionmethods support by @romalytvynenko in #1138 - Add attributes support on
FormRequest(e.g.#[*Parameter],#[SchemaName]) by @romalytvynenko in #1141 - Fix variadic placeholder request inference error by @romalytvynenko in #1139
Apr 10, 2026
v0.13.18
What’s Changed
- Fix memory leak in long-running processes (prevent extensions priority duplication) by @romalytvynenko in #1132
March 2026
Mar 27, 2026
v0.8.13 PRO
What’s Changed
- Fixed documenting of explicitly included (or not included) properties of nullable lazy properties
Mar 27, 2026
v0.13.17
What’s Changed
- Improved type templates inference by @romalytvynenko in #1112
- Improve type inference so
when(fromConditionaltrait) is supported by @romalytvynenko in #1113 - Soft delete methods support by @romalytvynenko in #1117
- Fix #[SchemaName] attribute not reflected in response description by @dbrekelmans in #1118
- Fix
requiredrule on arrays not setting minItems: 1 by @dbrekelmans in #1120 - Fix enum placed on array instead of items in OpenAPI spec by @dbrekelmans in #1119
New Contributors
- @dbrekelmans made their first contribution in #1118
Mar 17, 2026
v0.8.12 PRO
What’s Changed
- Improved support of lazy properties on data collections
Mar 16, 2026
v0.8.11 PRO
What’s Changed
- Improve support of lazy data collection properties
February 2026
Feb 20, 2026
v0.8.9 PRO
What’s Changed
- Fixed array annotated properties breaking in input context
Feb 16, 2026
v0.8.8 PRO
What’s Changed
- Fix documenting properties with
array-kind annotations