Create a 3.1.x branch

I guess the way I would do it is to first tag a new release 3.0.2 at the HEAD of the 3.0.x branch.
The 3.0.x branch could then be dedicated to its current ^9 || ^10 support, and would continue to depend on Voting API ^3 like it currently does.

Then I would branch off 3.1.x.
I would change the core version requirements to support ^10.3 || ^11, and change composer.json to use Voting API ^4 since that version of Voting API also supports ^10.3 || ^11.
After the requirements are changed, I would tag a new 3.1.1 release.

The end result would be:
A 3.0.x branch with a 3.0.2 tag on the HEAD
A 3.1.x branch with a 3.1.1 tag on the HEAD.

The difference between the two is initially the version of Drupal core that they support, but then 3.1.x can go on to make the changes necessary for D11.

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