Closed evoludolab closed 1 year ago
Yes, we've dropped PHP 8.0 support. 4.6.5 will be the last release that supports it. The reason is that PHP 8.0 is out of active support and we only support versions that are actively (and fully) supported by the PHP team.
@evoludolab We added a PHP check now, however, I wonder why Composer didn't fail. Usually, Composer fails if your PHP version is too old. Looks like you didn't run composer install
after pulling, or am I wrong here and Composer doesn't warn you?
@qwerty287 Indeed I didn't run composer after pulling but things went sideways already before, or at least without me being aware. I was merging upstream/master
into my PR #1631 with GitHub Desktop. I assume a hook then triggered the migration, which destroyed my DB. Everything happened behind the scenes and looked like the merge was successful. Only afterwards I was left with the unpleasant surprise of a corrupted users
table. With the warning sign in the title of #1618 I was of course aware that I would have to update at least to PHP 8.1 but not that it was needed before pulling. Hope that helps.
Detailed description of the problem [REQUIRED]
Updating to the latest HEAD (5a4c154 at time of writing) seems to have corrupted my SQLite database. Presumably this happened because I hadn't updated PHP beforehand (running PHP 8.0.26). After updating PHP, applying the migration again on my backup DB worked fine.
If my diagnosis is correct, would it be possible to check the PHP version first, throw an error/warning and skip the migration if the version is <8.1?
Output of the diagnostics [REQUIRED]
Browser and system
Safari, macOS 12