Skip to content
Snippets Groups Projects

fix(deps): update dependency api-platform/core to v3

Closed Reiter, Christoph requested to merge renovate/api-platform-core-3-x into main

This MR contains the following updates:

Package Type Update Change
api-platform/core (source) require major ^2.6 -> ^3.0

Release Notes

api-platform/core

v3.0.2

Compare Source

  • Metadata: generate skolem IRI by default, use genId: false to disable BC

v3.0.1

Compare Source

  • Symfony: don't use ArrayAdapter cache in production #​5027
  • Symfony: remove _api_exception_to_status leftovers (#​4992)
  • Serializer: support empty array as object (#​4999)
  • Chore: compatibility with PHP 8.2 (#​5024)
  • Symfony: resource class directories bc break (#​4982)
  • Symfony: exception_status bad merge (#​4981)
  • Graphql: remove unused service for ItemResolverFactory (#​4976)
  • Chore: document missing breaking changes on the 3.0.0-beta.1

v3.0.0

Compare Source

  • Metadata: CRUD on subresource with experimental write support (#​4932)
  • Symfony: 6.1 compatibility and remove 4.4 and 5.4 support (#​4851)
  • Symfony: removed the $exceptionOnNoToken parameter in ResourceAccessChecker::__construct() (#​4905)
  • Symfony: use conventional service names for Doctrine state providers and processors (#​4859)
  • Symfony: adjust mapping paths to the SF best practices for Bundles BC Resources/config/api_resources to config/api_resources (#​4853)
  • Symfony: src/ApiResource/ is the recommended place for API models (#​4874)
  • Cache: remove guzzle from the Varnish purger (#​4872)

Various cleanup in services and removal of backward compatibility layer.


Configuration

:date: Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

:no_bell: Ignore: Close this MR and you won't be reminded about this update again.


  • If you want to rebase/retry this MR, click this checkbox.

This MR has been generated by Renovate Bot.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • :warning: Artifact update problem

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

    :recycle: 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 MR's title to start with "rebase!" to trigger it manually

    The artifact failure details are included below:

    File name: composer.lock
    Command failed: composer update api-platform/core --with-dependencies --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
    Loading composer repositories with package information
    Updating dependencies
    Your requirements could not be resolved to an installable set of packages.
    
      Problem 1
        - Root composer.json requires api-platform/core ^3.0, found api-platform/core[v3.0.0, v3.0.1, v3.0.2] but these were not loaded, likely because it conflicts with another require.
      Problem 2
        - dbp/relay-core-bundle is locked to version v0.1.42 and an update of this package was not requested.
        - dbp/relay-core-bundle v0.1.42 requires api-platform/core ^2.6.6 -> found api-platform/core[v2.6.6, ..., v2.7.2] but it conflicts with your root composer.json require (^3.0).
    
    Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
    
  • Reiter, Christoph mentioned in issue #6

    mentioned in issue #6

  • Renovate Ignore Notification

    As this MR has been closed unmerged, Renovate will ignore this upgrade and you will not receive MRs for any future 3.x releases. However, if you upgrade to 3.x manually then Renovate will reenable minor and patch updates automatically.

    If this MR was closed by mistake or you changed your mind, you can simply rename this MR and you will soon get a fresh replacement MR opened.

Please register or sign in to reply
Loading