Open seb-enovate opened 2 months ago
Do you ise Deployer at master?
Hi Anton,
We are using version 7.3.3, if that is what you are asking?
Thanks
Seb
This is strange b/c deployed tagged version comes bunddled. No dependencies.
Not sure if this is helpful but we are installing Deployer like this:
composer require "deployer/deployer" "^7.0.1"
And then installing the AWS SDK like this:
composer require "aws/aws-sdk-php"
@antonmedv Sorry to chase, but we're still hitting this issue, would it help if we submitted a PR that adds a version constraint for the psr/http-message
that resolves the issue?
@mtwalsh I guess you're using master branch. Try to switch a version tag.
We are using the AWS SDK within our
deploy.php
file to fetch some data that we need for our deployments. However, since upgrading to more recent versions of the AWS SDK (version 3.303.4 in our case) we have been getting the following error when doing deploys (truncated for brevity):I believe the issue is that the AWS SDK changed their version constraint of the
psr/http-message
package to allow either 1.x or 2.x in this commit.Now Deployer's version constraint for the same package is
^1
, and I think this is allowing the package to jump to 2.x somehow.Running the following command in my project that uses Deployer fixes the issue:
I also note that in the output of that composer command it says the following:
So I think that the
psr/http-message
version constraint in Deployer'scomposer.json
needs to be updated to be more restrictive and prevent that package jumping to 2.x.Upvote & Fund