Andrei Ivascu

@RonSijm thank you for raising this, however I could not find any information about the `RegularExpression` attribute supporting neither `byte` nor `char` arrays. I wrote these tests to check and...

I think the optional parameters change can go into the next version, however the nullable reference type change will have to go into v6 since only after .NET 6 the...

@guipcarvalho the reason this PR or any other PR on `DateOnly` will not be merged into v4 master is described in my comment above https://github.com/AutoFixture/AutoFixture/pull/1305#issuecomment-1657997482. The current v5 preview version...

@evilbaschdi thank you for contributing to the project. I had only a brief look at it but it seems that the PR has a couple issues. First it depends on...

@evilbaschdi, while xUnit 3 might support the target frameworks you mentioned, this might not be the case for other libraries in the repo. The support of a runtime does not...

@evilbaschdi for now just rename the projects and namespaces to match the AutoFixture naming convention (i.e. `AutoFixture.Xunit3`). I'll have a look at it the implementation some time soon, as it's...

@evilbaschdi thank you for the information, I'll check as well what's going on there. I assume the convention is for the projects that want to release packages in the same...

@evilbaschdi the migration guide you referenced in your post, mentions two options for extension developers: - First is to just upgrade the existing package to xUnit v3. - Second is...

I'm at the moment trying to finish some work, in order to be able get my (long overdue) annual leave, so I can work on AutoFixture. It shouldn't be too...

@mycroes I resumed work a couple days ago. I'll post updates as I progress through the remaining backlog.