Open fooman opened 1 year ago
Hi @fooman. Thank you for your report. To speed up processing of this issue, make sure that you provided sufficient information.
Add a comment to assign the issue: @magento I am working on this
I have added jms/serializer:3.18.2
to my main Magento project and this worked better than doctrine/annotations:"^1.13"
as that downgraded jms/serializer
to 1.10.0
which errored elsewhere.
@fooman thank you for reporting this, this is a known issue that is currently being worked on internally. The .lock
file for our 2.4.6-develop
branch is locked peoperly to 3.18.2
, but yes there is no entry in composer.json
in Magento for some reason. Internal PR for that is going to be raised shortly to make it into the next beta 👍
Preconditions
Steps to reproduce
Expected result
Actual result
1.
The actual issue is this one https://github.com/allure-framework/allure-php-api/issues/117 and there is a fix proposed here https://github.com/allure-framework/allure-php-api/pull/119
Unfortunately that repo hasn't seen a new release in a while. As such it might be worth investigating adding some extra guardrails in place in this project - for example by adding
doctrine/annotations:"^1.13"
.