Request for updating GuzzleHttp dependency to the latest version

  • Resolved izabelademczuk

    (@izabelademczuk)


    7 months, 3 weeks ago

    We have noticed that the Authorizer plugin is using an outdated version of the GuzzleHttp library. This is causing conflicts with other plugins and tools we use in our project, as they require a newer version of this library. These dependency conflicts significantly hinder our project maintenance, as we are forced to modify your plugin, which is not an ideal solution.

    Is it possible for you to consider updating the GuzzleHttp dependency to its latest version in the upcoming release of the Authorizer plugin?

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Paul Ryan

    (@figureone)

    Definitely! We try to update all composer dependencies with each release, so guzzle must be getting pinned to the previous major version and we didn’t notice.

    Offhand, do you know which guzzle version is being used in your other libraries? We can target upgrading to that one.

    Thread Starter izabelademczuk

    (@izabelademczuk)

    Hey, thanks for the quick intervention, the plugin we use requires guzzleHttp ^7.0

    Thread Starter izabelademczuk

    (@izabelademczuk)

    And?

    Thread Starter izabelademczuk

    (@izabelademczuk)

    Hello, when can I expect an answer?

    Plugin Author Paul Ryan

    (@figureone)

    Apologies, we are juggling a lot right now. We might need to dig into this one a little further, I just checked our dependency versions with composer show and it is reporting we are on the latest version of guzzleHttp (7.8.1):

    guzzlehttp/guzzle 7.8.1 Guzzle is a ...
    guzzlehttp/promises 2.0.2 Guzzle promises library
    guzzlehttp/psr7 2.6.2 PSR-7 message implementation ...

    Also reflected in composer.lock: https://github.com/uhm-coe/authorizer/blob/master/composer.lock#L316-L322

    Can you provide more specifics on how you are patching Authorizer to a different guzzle version?

    Plugin Author Paul Ryan

    (@figureone)

    Closing this report as invalid. Authorizer uses guzzle 7.x. Very likely you misunderstood an error log that reported another plugin using guzzle 6.x, and a fatal error is triggered in guzzle 7.x if guzzle 6.x is autoloaded. We tried reaching out to the guzzle maintainers to patch guzzle 6.x to prevent the fatal error but they declined to fix guzzle 6.x since it is out of support.

    https://github.com/guzzle/guzzle/issues/3216

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Request for updating GuzzleHttp dependency to the latest version’ is closed to new replies.