@fkupper Whoops, that was me. (here #7)
I probably wrongly assumed that the fact that CI worked meant that it did not affect recent versions of Laravel.

I would like to apologize for the fact that the contribution guides are not so clear, I had yet to update them with respect to the module-symfony ones (where I am usually more active as a contributor).

I can solve all the doubts you have regarding the contribution guides in order to improve them in the process.

But basically:

1. I would need a PR in laravel-module-tests where, through a test failing, the CI of that repo confirms the issue.
2. I merge this PR with the patch to the main branch.
3. I re-run the tests of the PR from step 1 and the error should go away. That PR is merged.
4. I do a tag release of your fix. (rather, I add again what janhenkgerritsen did in Laravel5 fix issue with uploaded files Codeception#3429 ideally with a co-authored commit)

@fkupper Whoops, that was me. (here #7)
I probably wrongly assumed that the fact that CI worked meant that it did not affect recent versions of Laravel.

This is why tests are important. I really wanted to add a test for this but it doesn't fit the laravel-module-tests IMHO.

I would like to apologize for the fact that the contribution guides are not so clear, I had yet to update them with respect to the module-symfony ones (where I am usually more active as a contributor).

Please, no need for apologize! The guide is clear enough. What I mean is that the guide intends to test the module's methods and not the underlying code, therefore I did not see a place where the tests would fit.
If you have a strong opinion of how to introduce these tests, just point the way and I can add it, even if it is completely new test suit or something.

I can solve all the doubts you have regarding the contribution guides in order to improve them in the process.

But basically:

1. I would need a PR in [`laravel-module-tests`](https://github.com/Codeception/laravel-module-tests) where, through a test failing, the CI of that repo confirms the issue.

2. I merge this PR with the patch to the `main` branch.

3. I re-run the tests of the PR from step 1 and the error should go away. That PR is merged.

4. I do a tag release of your fix. (rather, I add again what **janhenkgerritsen** did in [Laravel5 fix issue with uploaded files Codeception#3429](https://github.com/Codeception/Codeception/pull/3429) ideally with a co-authored commit)

⬆️ This is very clear from the guide, don't worry! ;)

BTW, thanks for the effort of writing a proper reply with clear and meaningful content. 👏

Create a new test suite called IssuesCest and add a link to your PR in the dockblock. (eg. IssuesCest)

Create a new test suite called IssuesCest and add a link to your PR in the dockblock

Thank you!
I will have a look tomorrow, it is late in my timezone :)

Create a new test suite called IssuesCest and add a link to your PR in the dockblock. (eg. IssuesCest)

Tests added ✅
Codeception/laravel-module-tests#5

@fkupper I released your changes as version 2.0.1.

Thank you so much.