2.1.0 release?

+1, would be great to have a new beta :) The changes since beta1 seem fairly minor

Same here, needing this for a project I am upgrading to D10

Please, we need a release :)

beta2 would make life easier 🙏

Actually, this module has been compatible with Drupal 10 since December 2021, and has been passing the D10 tests for all that time. I know this because I was the one that made it compatible and I am the one who has been making changes to this module to keep it compatible as Drupal 10 core changed and evolved over the past 1+ year.

There are two reasons I haven't made a fixed point release for D10 yet:

The first is that D10 wasn't released until last month, and was subject to significant change until that point (and it DID changes significantly over the past year). D10 was released in December, and I personally have not had much free time in the past month. I also don't see much of a rush; there has been very little contribution from the community on this project, and almost no interest expressed in my plan last year to make a fixed point release, so this has taken a lower priority for my use of my limited free time.

The second is because going forward D10 support is going to be provided by the 2.0.x branch and the 8.x-1.x branch is going to be unsupported. I created the 2.0.x branch last month specifically for this purpose. But because major point versions are the only time some changes can be made, I want to get those changes in before I release a 2.0.0. Specifically, some things need to be properly deprecated in 8.x-1.x first, for example 📌 Deprecate Typed Data's fork of the Rules Context classes Fixed , so that they can be removed in 2.0.x. I don't want people doing an upgrade of a fixed point release before the deprecations and API changes are in place.

As I said, it has only been one month since the official D10 release, but this module has been D10 compatible for those who need it for more than a year. I have most of the deprecation and API work finished locally, and when I have time to get back to working on this module I will double check my work and push that out then make a release for 8.x-1.x and 2.0.x that supports upgrading between the two branches.

Thanks for all those details.
Makes total sense.

Is there a meta issue tracking blockers for a 2.0.0 release? Maybe we could repurpose this one?

That makes sense for a stable 2.0.0 but I don't see a reason not to release another beta on 8.x-1.x?