Skip to content

chore(deps): update dependency api-platform/json-schema to v4.3.1 - autoclosed#9230

Closed
renovate[bot] wants to merge 1 commit intodevelfrom
renovate/api-platform-json-schema-4.x
Closed

chore(deps): update dependency api-platform/json-schema to v4.3.1 - autoclosed#9230
renovate[bot] wants to merge 1 commit intodevelfrom
renovate/api-platform-json-schema-4.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 13, 2026

This PR contains the following updates:

Package Change Age Confidence
api-platform/json-schema (source) 4.2.204.3.1 age confidence

Release Notes

api-platform/core (api-platform/json-schema)

v4.3.1

Compare Source

What's Changed

New Contributors

Full Changelog: api-platform/core@v4.3.0...v4.3.1

v4.3.0

Compare Source

Features
Bug fixes
  • 263dbd8b2 fix: call object mapper with the expected class on 4.3 (#​7796)
  • af7c22749 fix(jsonld): use operation shortName for @​context URI with multiple ApiResources
  • 86b97d5ea fix(mcp): propagate session via processor context
  • 3b9ed3bd4 fix(laravel): make api-platform/mcp optional (#​7824) (#​7828)
  • 27cc4dbb3 fix(laravel): improve UI selection for documentation (#​7826)
  • e16f7ec4f fix(laravel): add init-scalar-ui.js to Laravel's assets (#​7825)
  • 5ca646111 fix(mcp): fallback to sdk handler when not found (#​7818)
  • 95ec407bf fix(jsonapi): wrong variable name during merge (#​7816)
  • 04c30b7ee fix(jsonapi): prevent double unwrapping of data.attributes with input DTOs
  • 191a46122 fix(serializer): apply API Platform name converter to input/output DTOs (#​7779)
  • 2e0b8ffb6 fix(serializer): prevent api_platform_output context from leaking to nested non-resource objects (#​7787)
  • c6236f313 fix(serializer): report all missing constructor arguments in instantiateObject
  • 31289b838 fix(symfony): make enable_docs a master switch for disabling documentation (#​7806)
  • 64247b050 fix(metadata): sort parameters by priority after pattern expansion (#​7788)
  • 813e4f793 fix(validator): missing required properties when using GroupSequence (#​7784)
  • 90dfc3554 fix(validator): handle nested groups and group sequences (#​7791)
  • 28834e6d6 fix(validator): validate entities after ObjectMapper transformation (#​7731)
  • 98b8efb68 fix(laravel): exclude .blade.php files from recursive class scan (#​7813)
  • cfdc22c1c fix(laravel): do not exclude custom primary keys matching HasMany foreign keys (#​7810)
  • 9f1109365 fix(hydra): example type - use @​type prefix per JSON-LD spec (#​7768)
  • 75ffdc43f fix(hydra): hide search key when there is parameter without filter (#​7773)
  • e0ba0068d fix(hydra): unique class @​id with subClassOf for semantic types (#​7771)
  • 9fdc6c27d fix(openapi): allow Operations to override global config in getPaginationParameters (#​7807)
  • 0f025e849 fix(state): handle partial pagination with object mapper (#​7769)
  • a2efb39e1 fix(elasticsearch): mono-repo v9 support (#​7766)
  • 332272c6f fix(jsonld): restore item_uri_template @​type resolution after 4.2 merge (#​7764)
  • 390056fbb fix(jsonld): item uri template type (#​7518)
  • f0b355984 fix(symfony): use AsCommand description parameter for console commands (#​7763)
  • 23840f9df fix(symfony): publish mercure updates for all resources of an entity (#​7774)
  • c624daf68 fix(symfony): allow toggling GraphQL Playground to ensure BC
  • c741bd62e fix: add missing RPC messenger handler for Symfony 8.1 compatibility
  • a4715f063 fix(doctrine): enforce api-platform/serializer dependency (#​7781)
  • 149fe24a1 fix(doctrine): throw exception if property is null for the doctrine filters (#​7681)
  • 17b6ff221 fix(jsonschema): name collision when an operation name is already used by another class (#​7778)
  • 4f6c4e1b4 fix(laravel): object-mapper / mcp-bundle versions
Breaking changes
  • JSON-LD @type with output and itemUriTemplate: When using output with itemUriTemplate on a collection operation, the JSON-LD @type now uses the resource class name instead of the output DTO class name for semantic consistency with itemUriTemplate behavior. Update any client code that relies on the DTO class name in @type.
  • Doctrine filters require explicit property (#​7681): Doctrine parameter-based filters (ExactFilter, IriFilter, PartialSearchFilter, UuidFilter) now throw InvalidArgumentException if the property attribute is missing. If you have filter parameters without an explicit property, you must either add one or use the :property placeholder in your parameter name.
  • Readonly Doctrine entities lose PUT & PATCH (#​7453): Entities marked as readonly via Doctrine metadata ($classMetadata->markReadOnly()) will no longer expose PUT and PATCH operations. Clients sending PUT/PATCH to these resources will receive a 404. If you need write operations on readonly entities, explicitly define them in your ApiResource attribute.
Behavioral changes
  • Hydra class @id now always uses #ShortName (#​7771): Hydra documentation classes now consistently use #ShortName as their @id instead of schema.org type URIs (e.g. schema:Product). This resolves class identifier collisions when multiple resources shared the same semantic type, which previously caused api-doc-parser conflation. Semantic types configured via types are now exposed through rdfs:subClassOf. Clients should expect class @id and property range changes in the Hydra documentation if resources had custom types configured.
  • isGranted evaluated before provider (#​7500): Security expressions are now evaluated before the state provider runs. Expressions that do not reference the object variable will be checked earlier (at the pre_read stage), improving security by preventing unnecessary database queries on unauthorized requests. Expressions that reference object still wait for the provider to resolve the entity. Review any security expressions that relied on provider side-effects running before authorization.
  • LDP-compliant response headers (#​6917): API responses now include Allow and Accept-Post headers per the Linked Data Platform specification. These are informational headers that help clients discover API capabilities and should not break existing integrations.
  • Scalar API Reference UI (#​7817): Scalar is now available as an alternative documentation UI alongside Swagger UI. It is enabled by default when TwigBundle is available. Access it via ?ui=scalar. To disable it, set enable_scalar: false in your API Platform configuration.

v4.2.22

Compare Source

What's Changed
New Contributors

Full Changelog: api-platform/core@v4.2.21...v4.2.22

v4.2.21

Compare Source

Bug fixes
  • 20ced5fca fix(laravel): clear SkolemIriConverter state between requests (#​7838)
  • 2b2b7bca2 fix(filter): use correct type for int-backed enums in BackedEnumFilter
  • 42a2d7fc6 fix(symfony): register DateTimeValueObjectTransformer for JsonStreamer (#​7839)
  • 63e6b57f8 fix(openapi): correct redocly openapi errors (#​7834)
  • 6a472a2db fix(jsonapi): swap arguments in DefinitionNameFactory::create() call
  • bbfd4cafa fix(filter): do not nest array while generating default schema (#​7832)
  • c20a41c20 fix(symfony): clear SkolemIriConverter state between requests via ResetInterface (#​7829)
  • d6ecbe122 fix(serializer): Use serializer when denormalizing relation inside Input (#​7830)
  • da6232468 fix(metadata): allow GraphQL-only resources without identifiers (#​3975) (#​7836)
  • f4002902a fix(state): on creation, give expected class to object mapper (#​7795)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovate label Mar 13, 2026
@renovate renovate bot enabled auto-merge March 13, 2026 20:44
@renovate
Copy link
Contributor Author

renovate bot commented Mar 13, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: api/composer.lock
Command failed: composer update api-platform/json-schema:4.3.1 --with-dependencies --ignore-platform-req=ext-* --ignore-platform-req=lib-* --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins --minimal-changes
Loading composer repositories with package information
Dependency api-platform/metadata is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency symfony/console is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency symfony/property-info is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency symfony/serializer is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires api-platform/json-schema 4.3.1 -> satisfiable by api-platform/json-schema[v4.3.1].
    - api-platform/json-schema v4.3.1 requires api-platform/metadata ^4.3 -> found api-platform/metadata[v4.3.0, v4.3.1] but it conflicts with your root composer.json require (4.2.20).
  Problem 2
    - api-platform/hydra is locked to version v4.2.17 and an update of this package was not requested.
    - api-platform/hydra v4.2.17 requires api-platform/json-schema ^4.2 -> satisfiable by api-platform/json-schema[v4.3.1].
    - api-platform/json-schema v4.3.1 requires api-platform/metadata ^4.3 -> found api-platform/metadata[v4.3.0, v4.3.1] but it conflicts with your root composer.json require (4.2.20).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

@renovate renovate bot force-pushed the renovate/api-platform-json-schema-4.x branch from 215be2b to 3e6c329 Compare March 18, 2026 01:16
@renovate renovate bot force-pushed the renovate/api-platform-json-schema-4.x branch from 3e6c329 to 49ee685 Compare March 20, 2026 12:56
@renovate renovate bot changed the title chore(deps): update dependency api-platform/json-schema to v4.3.0 chore(deps): update dependency api-platform/json-schema to v4.3.1 Mar 20, 2026
@renovate renovate bot changed the title chore(deps): update dependency api-platform/json-schema to v4.3.1 chore(deps): update dependency api-platform/json-schema to v4.3.1 - autoclosed Mar 21, 2026
@renovate renovate bot closed this Mar 21, 2026
auto-merge was automatically disabled March 21, 2026 21:03

Pull request was closed

@renovate renovate bot deleted the renovate/api-platform-json-schema-4.x branch March 21, 2026 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants