Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has a contribution guide which I suggest you to read.

In short:

• Always add tests
• Keep backward compatibility (see https://symfony.com/bc).
• Bug fixes must be submitted against the lowest maintained branch where they apply (see https://symfony.com/releases)
• Features and deprecations must be submitted against the 6.3 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

Hey!

Thanks for your PR. You are targeting branch "6.3" but it seems your PR description refers to branch "6.3 (maybe 6.2?)".
Could you update the PR description or change target branch? This helps core maintainers a lot.

Cheers!

Carsonbot

This would still break cases where objects of this class are passed around but the called code expects an instance of Monolog's Logger class (which we now no longer would extend).

There are still two paint points with that solution:

• the deprecation about the Logger class from Monolog class would not go away
• How can we communicate that the class will no longer extend Monolog's Logger class in 7.0 (i.e. trigger a proper deprecation) so that people can prepare their applications?