Add nullable type on implicit types

[Quetzacoalt91]

Questions	Answers
Description?	<b>Deprecated</b>: PrestaShop\Module\AutoUpgrade\Models\PrestashopRelease::__construct(): Implicitly marking parameter $distribution as nullable is deprecated, the explicit nullable type must be used instead in <b>modules/autoupgrade/classes/Models/PrestashopRelease.php</b> on line <b>47</b><br />
Type?	bug fix
BC breaks?	Nope
Deprecations?	Nope
Fixed ticket?	Fix reported issue via Error reporting modal of Update Assistant
Sponsor company	@PrestaShopCorp
How to test?	Running PrestaShop on PHP 8.4 with the error reporting as -1, plus _PS_DISPLAY_COMPATIBILITY_WARNING_ as true in config/defines.inc.php should trigger the error on the dev branch.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[AureRita]

Hello @Quetzacoalt91

Thank you for your PR, I tested it and with php 8.4, event without the error reporting as -1, i've many other deprecated call that give me an error on update assistant as you can see :

Capture.video.du.2025-11-28.15-19-26.mp4

I expect that screen 'll help you to find the different part of the deprecation

Waiting for feedbacks

[Quetzacoalt91]

All these reports are related to files stored in vendor/, on which I have no control because of the PHP compatibility range we currently have.

This is fine at the moment and will be handled in a broader topic.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[AureRita]

Hi @Quetzacoalt91

Thank you for your PR, I tested it and it seems to works as you can see :

(on top of the screen, you have a previous version with the error underline, on bot you have the correction)

Tested on :
9.0.0 php 8.4

FI: as said before "reports are related to files stored in vendor/" are not related to this PR, so it not blocked this PR

Because the PR seems to works as expected, It's QA ✔️

Thank you