Drupal 9 users being updated to 3.0.0-beta1 incorrectly

After discussion in Drupal Slack's #drupalorg this is what was suggested:

1. Create a new 4.x branch and 4.0.0 release based on the current state of 3.x.
2. Revert all Drupal 10 changes on the 3.x branch making 3.x match 8.x-2.x.
3. Create a new 3.0.1 release (which will be D9-only).
4. Update Drupal 10 upgrade instructions on the project page to read: composer require drupal/csv_serialization:^2.0 || ^3.0 || ^4.0

4.x becomes the Drupal 10 branch and 3.x becomes the Drupal 9 branch.

I believe the changes suggested in #4 should minimize the disruption to users, but I am going to mark this as "needs review" for at least 1 week to allow for any concerns to be raised.

This sounds like quite a sensible path forward.

Thankfully I saw this before trying to upgrade!

I don't quite understand the composer require drupal/csv_serialization:^2.0 || ^3.0 || ^4.0 aspect, but that may just be lack of knowledge of composer version pinning. Would it not simply be ^4.0 for D10?

3.0.1 has been released with Drupal 9.4+ support.
4.x branch has been opened.
4.0.0 has been released with Drupal 10 support.
Issues in queue marked for 3.x have been updated to point to 4.x.
Upgrade notes/instructions have been updated on the project page (see below).

It is not possible to support both Drupal 9.x and 10.x in a single release 🐛 CsvEncoder::encode must be compatible with Symfony\Component\Serializer\Encoder\EncoderInterface::encode Fixed of this module due to a breaking change in EncoderInterface::encode() between Symfony 4.4 (D9) and Symfony 6.2 (D10). When preparing for an upgrade to Drupal 10 we recommend that you widen your Composer version constraints to allow either 3.x or 4.x: composer require drupal/csv_serialization:^3.0 || ^4.0. This will allow the module to be automatically upgraded when you upgrade Drupal core.

D10 sites using views_data_export will be blocked from upgrading until 📌 Allow csv_serialization 4.x Needs review is in

@acbramly, Thanks you for the #11, the patch in #3397869 is working for me.

Automatically closed - issue fixed for 2 weeks with no activity.