Allow PHPUnit 12 #4624

staabm · 2025-12-09T09:04:43Z

Before

Time: 04:37.104, Memory: 688.50 MB
Generating code coverage report in PHPUnit XML format ... done [00:51.395]

After upgrading to PHPUnit 12

Time: 04:23.595, Memory: 678.50 MB
Generating code coverage report in PHPUnit XML format ... done [00:21.631]

After adding --exclude-source-from-xml-coverage

Time: 04:16.807, Memory: 634.50 MB
Generating code coverage report in PHPUnit XML format ... done [00:21.631]

ondrejmirtes · 2025-12-09T09:17:54Z

I'd prefer to have just 12 in composer.json, and then downgrade in action yamls in lower unsupported PHP versions.

So ideally PHPUnit 12 on PHP 8.3+ in the composer.json files, downgrade to 9 on PHP < 8.3. Infection could only run on PHP 8.3+.

To have a lock file and then multiple version ranges for a package in composer.json doesn't make sense.

Also don't forget to commit the tests/ lock file 😊

staabm · 2025-12-09T13:04:35Z

hm this would mean to update most nette/ packages in the same step, as we would also raise phpstan-src/composer.json to php 8.3?

ondrejmirtes · 2025-12-09T14:33:39Z

Updating the Nette packages is hard, they probably drop PHP 7.4 in versions that support 8.3.

And some packages we will probably never be able to upgrade, like nette/di. There's a longer story, but 3.1.15 (the one that is copied in composer.json in its entirety) is the one that works for me, newer versions break stuff.

staabm · 2025-12-09T14:56:13Z

so maybe use PHPUnit 9 on old php versions, PHPUnit 11 on 8.1,8.2 and PHPUnit 12+ on 8.3+ ?

alternatively: use PHPUnit12 only in the mutation testing job and leave everything else on the current state of things

ondrejmirtes · 2025-12-09T14:57:55Z

so maybe use PHPUnit 9 on old php versions, PHPUnit 11 on 8.1,8.2 and PHPUnit 12+ on 8.3+ ?

I'm a bit slow, what would it solve in regards to Nette packages?

staabm · 2025-12-09T15:09:31Z

I'm a bit slow, what would it solve in regards to Nette packages?

if I declare PHPUnit12 on top of PHPUnit11, the php runtime version will decide which phpunit version it will run on.
I can leave min php version as is

if I update to PHPUnit12 only, I need to raise the min php version to 8.3 and this means I need to raise nette/* packages

staabm · 2025-12-09T15:34:00Z

~~ok, lets see paratestphp/paratest#1057 :)~~

ondrejmirtes · 2025-12-09T19:48:28Z

Alright, so there will be PHPUnit 11 in composer.json, and actions will sometimes downgrade to PHPUnit 9, and sometimes upgrade to PHPUnit 12? So why doesn't having PHPUnit 12 in composer.json work? (Why composer require phpunit v12 works?)

staabm · 2025-12-09T19:56:49Z

So why doesn't having PHPUnit 12 in composer.json work? (Why composer require phpunit v12 works?)

it doesn't work.

➜  phpstan-src git:(2.1.x) ✗ composer require phpunit/phpunit ^12 --dev 
./composer.json has been updated
Running composer update phpunit/phpunit
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires phpunit/phpunit ^12 -> satisfiable by phpunit/phpunit[12.0.0, ..., 12.5.x-dev].
    - phpunit/phpunit[12.0.0, ..., 12.5.x-dev] require php >=8.3 -> your php version (8.2.99; overridden via config.platform, actual: 8.5.0) does not satisfy that requirement.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

ondrejmirtes · 2025-12-09T19:58:15Z

Add --ignore-platform-reqs?

staabm · 2025-12-09T20:08:46Z

doesn't work either.

➜  phpstan-src git:(2.1.x) ✗ composer require phpunit/phpunit ^12 --dev  --ignore-platform-reqs
./composer.json has been updated
Running composer update phpunit/phpunit
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires phpunit/phpunit ^12 -> satisfiable by phpunit/phpunit[12.0.0, ..., 12.5.x-dev].
    - phpunit/phpunit[12.0.0, ..., 12.0.1] require phpunit/php-code-coverage ^12.0.0 -> found phpunit/php-code-coverage[dev-main, 12.0.0, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.0.8, ..., 12.0.10] require phpunit/php-code-coverage ^12.1.0 -> found phpunit/php-code-coverage[dev-main, 12.1.0, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.0.2, ..., 12.0.3] require phpunit/php-code-coverage ^12.0.2 -> found phpunit/php-code-coverage[dev-main, 12.0.2, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.0.4, ..., 12.0.5] require phpunit/php-code-coverage ^12.0.3 -> found phpunit/php-code-coverage[dev-main, 12.0.3, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.0.6, ..., 12.0.7] require phpunit/php-code-coverage ^12.0.4 -> found phpunit/php-code-coverage[dev-main, 12.0.4, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.1.0, ..., 12.1.4] require phpunit/php-code-coverage ^12.1.2 -> found phpunit/php-code-coverage[dev-main, 12.1.2, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.1.5, ..., 12.1.6] require phpunit/php-code-coverage ^12.2.1 -> found phpunit/php-code-coverage[dev-main, 12.2.1, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.2.0, ..., 12.2.2] require phpunit/php-code-coverage ^12.3.0 -> found phpunit/php-code-coverage[dev-main, 12.3.0, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.2.3, ..., 12.2.7] require phpunit/php-code-coverage ^12.3.1 -> found phpunit/php-code-coverage[dev-main, 12.3.1, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.2.8, ..., 12.3.6] require phpunit/php-code-coverage ^12.3.2 -> found phpunit/php-code-coverage[dev-main, 12.3.2, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.3.9, ..., 12.3.11] require phpunit/php-code-coverage ^12.3.7 -> found phpunit/php-code-coverage[dev-main, 12.3.7, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.3.12, ..., 12.3.14] require phpunit/php-code-coverage ^12.3.8 -> found phpunit/php-code-coverage[dev-main, 12.3.8, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit 12.3.7 requires phpunit/php-code-coverage ^12.3.3 -> found phpunit/php-code-coverage[dev-main, 12.3.3, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit 12.3.8 requires phpunit/php-code-coverage ^12.3.6 -> found phpunit/php-code-coverage[dev-main, 12.3.6, ..., 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.3.15, ..., 12.4.5] require phpunit/php-code-coverage ^12.4.0 -> found phpunit/php-code-coverage[dev-main, 12.4.0, 12.5.0, 12.5.1, 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.5.0, ..., 12.5.1] require phpunit/php-code-coverage ^12.5.0 -> found phpunit/php-code-coverage[dev-main, 12.5.0, 12.5.1, 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - phpunit/phpunit[12.5.2, ..., 12.5.x-dev] require phpunit/php-code-coverage ^12.5.1 -> found phpunit/php-code-coverage[dev-main, 12.5.1, 12.5.x-dev (alias of dev-main)] but the package is fixed to 11.0.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

but I don't get your point. do you want to have settings in composer.json which only work when invoked with --ignore-platform-reqs?

ondrejmirtes · 2025-12-09T20:14:01Z

I updated php-merge to 4.1.2
I ran composer require sebastian/diff:^7 phpunit/phpunit:^12 --ignore-platform-reqs -W and it worked on my machine. The only hiccup is that one is non-dev dep and another one is dev dep, but Composer needs them updated at the same.

do you want to have settings in composer.json

It wouldn't be committed to composer.json. It'd only be in GitHub Actions in places where we want PHPUnit v12.

staabm · 2025-12-09T20:17:47Z

yeah, but what you describe is what this PR is already doing?

ondrejmirtes · 2025-12-09T20:31:19Z

That's good news, I assumed it doesn't work, didn't check the log.

I'd like to have PHPUnit 12 on 8.3+ in normal tests run too.

ondrejmirtes · 2025-12-09T20:31:48Z

The failures about mocks vs. stubs should be fixed in a separate PR merged before this one 😊

staabm · 2025-12-09T20:35:21Z

The failures about mocks vs. stubs should be fixed in a separate PR merged before this one 😊

phpunit warnings are fixed in #4625

will do another PR for the stubs

staabm · 2025-12-10T07:05:42Z

.github/workflows/tests.yml

+        run: "vendor/bin/phpunit --check-php-configuration"
+
+      - name: "Tests"
+        run: "php tests/vendor/bin/paratest --runner WrapperRunner --no-coverage"


I need to call paratest directly, instead of using make tests which would trigger composer install --working-dir tests, and this errors because of platform-requirement problems with:

composer install --working-dir tests Installing dependencies from lock file (including require-dev) Verifying lock file contents can be installed on current platform. Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - brianium/paratest is locked to version v7.16.0 and an update of this package was not requested. - brianium/paratest v7.16.0 requires php ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.2.99; overridden via config.platform, actual: 8.3.28) does not satisfy that requirement. Problem 2 - phpunit/php-code-coverage is locked to version 12.5.1 and an update of this package was not requested. - phpunit/php-code-coverage 12.5.1 requires php >=8.3 -> your php version (8.2.99; overridden via config.platform, actual: 8.3.28) does not satisfy that requirement.

see https://github.com/phpstan/phpstan-src/actions/runs/20089728006/job/57634537245?pr=4624

in case this is fine, I think I can remove the symfony/* packages again from
composer require --dev phpunit/phpunit:^12 brianium/paratest:^7.16 symfony/process:^7 symfony/string:^7 symfony/console:^7 --update-with-dependencies --ignore-platform-reqs --working-dir=tests

staabm · 2025-12-10T07:11:11Z

phpunit.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="vendor/phpunit/phpunit/phpunit.xsd" bootstrap="tests/bootstrap.php" cacheResult="false" colors="true" executionOrder="random" failOnRisky="true" failOnWarning="true" failOnEmptyTestSuite="true" beStrictAboutChangesToGlobalState="true" beStrictAboutOutputDuringTests="true" cacheDirectory="tmp/.phpunit.cache" beStrictAboutCoverageMetadata="true" displayDetailsOnPhpunitDeprecations="true" displayDetailsOnIncompleteTests="true">
+<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="vendor/phpunit/phpunit/phpunit.xsd" bootstrap="tests/bootstrap.php" cacheResult="false" colors="true" executionOrder="random" failOnRisky="true" failOnWarning="true" failOnPhpunitWarning="false" failOnEmptyTestSuite="true" beStrictAboutChangesToGlobalState="true" beStrictAboutOutputDuringTests="true" cacheDirectory="tmp/.phpunit.cache" beStrictAboutCoverageMetadata="true" displayDetailsOnPhpunitDeprecations="true" displayDetailsOnIncompleteTests="true">


I disabled exit-code=1 on phpunit warnings because we currently get warnings like

1) PHPStan\Analyser\LegacyNodeScopeResolverTest::testTypeFromMethodPhpDocs * Data set #5 provided by PHPStan\Analyser\LegacyNodeScopeResolverTest::dataTypeFromMethodPhpDocs has more arguments (3) than the test method accepts (2) * Data set #9 provided by PHPStan\Analyser\LegacyNodeScopeResolverTest::dataTypeFromMethodPhpDocs has more arguments (3) than the test method accepts (2) * Data set #18 provided by PHPStan\Analyser\LegacyNodeScopeResolverTest::dataTypeFromMethodPhpDocs has more arguments (3) than the test method accepts (2) * Data set #19 provided by PHPStan\Analyser\LegacyNodeScopeResolverTest::dataTypeFromMethodPhpDocs has more arguments (3) than the test method accepts (2) * Data set #5 provided by PHPStan\Analyser\LegacyNodeScopeResolverTest::dataTypeFromMethodPhpDocs has more arguments (3) than the test method accepts (2) * Data set #9 provided by PHPStan\Analyser\LegacyNodeScopeResolverTest::dataTypeFromMethodPhpDocs has more arguments (3) than the test method accepts (2) * Data set #18 provided by PHPStan\Analyser\LegacyNodeScopeResolverTest::dataTypeFromMethodPhpDocs has more arguments (3) than the test method accepts (2) * Data set #19 provided by PHPStan\Analyser\LegacyNodeScopeResolverTest::dataTypeFromMethodPhpDocs has more arguments (3) than the test method accepts (2) /home/runner/work/phpstan-src/phpstan-src/tests/PHPStan/Analyser/LegacyNodeScopeResolverTest.php:3764 2) PHPStan\Rules\Methods\OverridingMethodRuleTest::testOverridingFinalMethod * Data set #0 provided by PHPStan\Rules\Methods\OverridingMethodRuleTest::dataOverridingFinalMethod has more arguments (3) than the test method accepts (2) * Data set #1 provided by PHPStan\Rules\Methods\OverridingMethodRuleTest::dataOverridingFinalMethod has more arguments (3) than the test method accepts (2) * Data set #0 provided by PHPStan\Rules\Methods\OverridingMethodRuleTest::dataOverridingFinalMethod has more arguments (3) than the test method accepts (2) * Data set #1 provided by PHPStan\Rules\Methods\OverridingMethodRuleTest::dataOverridingFinalMethod has more arguments (3) than the test method accepts (2) /home/runner/work/phpstan-src/phpstan-src/tests/PHPStan/Rules/Methods/OverridingMethodRuleTest.php:59 3) PHPStan\Rules\Methods\OverridingMethodRuleTest::testBug3403 * Data set #0 provided by PHPStan\Rules\Methods\OverridingMethodRuleTest::dataOverridingFinalMethod has more arguments (3) than the test method accepts (1) * Data set #1 provided by PHPStan\Rules\Methods\OverridingMethodRuleTest::dataOverridingFinalMethod has more arguments (3) than the test method accepts (1) * Data set #0 provided by PHPStan\Rules\Methods\OverridingMethodRuleTest::dataOverridingFinalMethod has more arguments (3) than the test method accepts (1) * Data set #1 provided by PHPStan\Rules\Methods\OverridingMethodRuleTest::dataOverridingFinalMethod has more arguments (3) than the test method accepts (1) /home/runner/work/phpstan-src/phpstan-src/tests/PHPStan/Rules/Methods/OverridingMethodRuleTest.php:325

which we cannot ignore using validateArgumentCount #[DataProvider] parameter because this parameter doesn't exist on PHPUnit 11.x:

XDEBUG_MODE=off php tests/vendor/bin/paratest --runner WrapperRunner --no-coverage ParaTest v7.8.4 upon PHPUnit 11.5.45 by Sebastian Bergmann and contributors. In AttributeParser.php line 421: Invalid attribute PHPUnit\Framework\Attributes\DataProvider for method PHPS tan\Rules\Methods\OverridingMethodRuleTest::testOverridingFinalMethod() in /home/runner/work/phpstan-src/phpstan-src/tests/PHPStan/Rules/Methods/Overr idingMethodRuleTest.php:59 Unknown named parameter $validateArgumentCount paratest [--functional] [-m|--max-batch-size MAX-BATCH-SIZE] [--no-test-tokens] [--passthru-php PASSTHRU-PHP] [-p|--processes PROCESSES] [--runner RUNNER] [--tmp-dir TMP-DIR] [-v|--verbose] [--bootstrap BOOTSTRAP] [-c|--configuration CONFIGURATION] [--no-configuration] [--cache-directory CACHE-DIRECTORY] [--testsuite TESTSUITE] [--exclude-testsuite EXCLUDE-TESTSUITE] [--group GROUP] [--exclude-group EXCLUDE-GROUP] [--filter FILTER] [--process-isolation] [--strict-coverage] [--strict-global-state] [--disallow-test-output] [--dont-report-useless-tests] [--stop-on-defect] [--stop-on-error] [--stop-on-failure] [--stop-on-warning] [--stop-on-risky] [--stop-on-skipped] [--stop-on-incomplete] [--fail-on-incomplete] [--fail-on-risky] [--fail-on-skipped] [--fail-on-warning] [--fail-on-deprecation] [--order-by ORDER-BY] [--random-order-seed RANDOM-ORDER-SEED] [--colors [COLORS]] [--no-progress] [--display-incomplete] [--display-skipped] [--display-deprecations] [--display-errors] [--display-notices] [--display-warnings make: *** [Makefile:6: tests] Error 1 Error: Process completed with exit code 2.

alternatively we could drop the validateArgumentCount parameter in the downgrading process

ondrejmirtes · 2025-12-10T07:56:45Z

Yeah, maintaining this is getting more and more complicated. At least we can look forward to dropping some of the complexity when PHPStan 3.0 will only support PHP 8.1+.

phpstan-bot · 2025-12-10T08:01:45Z

This pull request has been marked as ready for review.

ondrejmirtes · 2025-12-10T08:02:47Z

Thank you!

staabm force-pushed the unit12 branch 3 times, most recently from 2f4c833 to 23c53ac Compare December 10, 2025 06:56

staabm commented Dec 10, 2025

View reviewed changes

staabm force-pushed the unit12 branch from 633fb59 to 5637e71 Compare December 10, 2025 07:12

staabm and others added 8 commits December 10, 2025 08:54

Allow PHPUnit 12

ddb07ae

Update tests.yml

0e13538

fix

4fecb10

soft allow phpunit 12

38e5d74

Update composer.lock

970fe6f

fix

f9a786f

Discard changes to tests/composer.lock

0f209ab

Discard changes to composer.lock

3e6a379

staabm and others added 19 commits December 10, 2025 08:54

Update composer.lock

a352da2

Update composer.lock

8ec00db

Upgrade PHPUnit with Paratest to speedup coverage generation

2ccfd39

Discard changes to composer.json

d9e87e6

Discard changes to tests/composer.json

58610c3

Discard changes to composer.lock

add0bda

Discard changes to tests/composer.lock

724fe7b

composer update ondrejmirtes/php-merge

7eec0e0

Update tests.yml

cef7953

Update tests.yml

c19ee8e

Update tests.yml

25cdae6

Update phpunit.xml

0bb0ec1

Update tests.yml

385f523

Update tests.yml

a310886

Update tests.yml

9c82124

Update tests.yml

1a11155

Update tests.yml

60ddd1b

Update tests.yml

c784d02

cleanup

0910050

ondrejmirtes force-pushed the unit12 branch from 5637e71 to 0910050 Compare December 10, 2025 07:54

staabm marked this pull request as ready for review December 10, 2025 08:01

ondrejmirtes merged commit f7ccea9 into phpstan:2.1.x Dec 10, 2025
633 of 635 checks passed

staabm deleted the unit12 branch December 10, 2025 08:03

Allow PHPUnit 12 #4624

Allow PHPUnit 12 #4624

Conversation

staabm commented Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ondrejmirtes commented Dec 9, 2025

Uh oh!

staabm commented Dec 9, 2025

Uh oh!

ondrejmirtes commented Dec 9, 2025

Uh oh!

staabm commented Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ondrejmirtes commented Dec 9, 2025

Uh oh!

staabm commented Dec 9, 2025

Uh oh!

staabm commented Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ondrejmirtes commented Dec 9, 2025

Uh oh!

staabm commented Dec 9, 2025

Uh oh!

ondrejmirtes commented Dec 9, 2025

Uh oh!

staabm commented Dec 9, 2025

Uh oh!

ondrejmirtes commented Dec 9, 2025

Uh oh!

staabm commented Dec 9, 2025

Uh oh!

ondrejmirtes commented Dec 9, 2025

Uh oh!

ondrejmirtes commented Dec 9, 2025

Uh oh!

staabm commented Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

staabm Dec 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

staabm Dec 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

staabm Dec 10, 2025

Choose a reason for hiding this comment

Uh oh!

ondrejmirtes commented Dec 10, 2025

Uh oh!

phpstan-bot commented Dec 10, 2025

Uh oh!

Uh oh!

ondrejmirtes commented Dec 10, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

staabm commented Dec 9, 2025 •

edited

Loading

staabm commented Dec 9, 2025 •

edited

Loading

staabm commented Dec 9, 2025 •

edited

Loading

staabm commented Dec 9, 2025 •

edited

Loading

staabm Dec 10, 2025 •

edited

Loading

staabm Dec 10, 2025 •

edited

Loading