-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.x] Can't update sentry package to 4.x from symfony 4.4.19 #440
Comments
Hi there, On 4.x we allow the following versions: Line 32 in 24b1dac
This should also include Symfony Are you able to share your |
|
Just hit this issue as well so cannot install it on |
@carlcasbolt can you please show us the output for: composer why-not "symfony/security-core:^3.4.43||^4.4.11|^5.0.11" And if possible share your full |
output
|
console version
I'll see if pulling the version up to the latest 4.4.x helps |
This is the culrprit of the issue: in the |
getting a different error now that I have updated all packages Console version:
Command:
|
Sadly, you're one more person that got hit by #379. Apart from writing some note in the README about the issue, I don't think there is nothing on our side that we can do to improve things: will do it asap as it's a too frequent issue to ignore it |
Since the original author of this issue didn't answer anymore I take for granted that the issue has been solved. Feel free to reopen should you have still need for help |
FYI this seems related composer/composer#9749 |
Environment
Which SDK and version?
PHP 7.4
Steps to Reproduce
Hello ,
I can't upgrade the symfony package to the latest version because the symfony/security module must be in ^4.4.11 on your package.
I encountred this error :
sentry/sentry-symfony [4.0.0, ..., 4.0.1] require symfony/security-core ^3.4.43||^4.4.11|^5.0.11 -> found symfony/security-core [v3.4.43, ..., v3.4.47, v4.4.11, ..., v4.4.19, v5.0.11, ..., v5.2.3] but it conflicts with another require.
Would it be possible to allow the use of 4.4.19 of this package?
Sincerely
The text was updated successfully, but these errors were encountered: