Rules requires earlier version of Typed_data not compatible with Drupal 10.3

This dependency is deliberate.

Rules 3 will not work with core Drupal 10.3, so do not upgrade your version of core yet if you need Rules - and in fact the Typed Data dependency should prevent you from upgrading core and should prevent you from having problems. This is being worked on and will be fixed in the near future. See 📌 [10.3] Update ConditionManager to support PHP Attributes Active .

Core Drupal 10.3 introduced a change that broke Rules 3. Fixing that would require major changes, and those changes would break compatibility with Drupal 10.2 and Drupal 9.

Rules 4 was created so that we can make these changes to support Drupal 10.3 and Drupal 11 without breaking support for earlier versions of core.

So Rules 3 is for Drupal 10.2 and below, Rules 4 is for Drupal 10.3 and above. Rules 4 uses Typed Data 2, while Rules 3 uses Typed Data 1.

Rules 4 is not ready to use on core Drupal 10.3 yet - that is why there is no release.

Thank you for the explanation.

So when can we expect to see a solution? IMHO this should not be marked "Fixed" until we Rules-users can upgrade to D10.3.

/Thomas

@sl27257: This is a support issue. "Fixed" means the question has been answered. It was answered completely. This issue is "fixed".

So when can we expect to see a solution?

If you want to hire me and pay me, then you will get to dictate when and how I work on this issue.

Until then, *I* get to decide how I spend my free time. I am not employed to work on Drupal in any way. NO ONE is employed to work on the Rules module in any way. If it is important to *you* that a fix happens promptly then perhaps YOU can spend dozens of unpaid free hours contributing back to the community. OR perhaps you can fund the development done by volunteers like myself. If you don't care enough to put your own time or money into the fix, then please shut up.

That was a polite question!!!

If you check my profile you will see that I am not either affiliated with Drupal. I am handling another module on my "spare time" so I know exactly what you are talking about!

Unfortunately we are only something like less than 5% nowadays that are NOT working on Drupal as a PAID job. And given the extensive updates from D7 to D8 and now all the incompatible changes between the different D9, D10, D11 we have seen causing a lot of problem for us doing things on our spare time!

But if I get answers like yours I will mark my module as unsupported. It is not so funny to get comments like yours when you are doing something for fun and still being somewhat proud that you have achieved over the years!

That said!

It sounds like that you are somewhat stressed out, TR. I can understand that. I too feel a little stressed out sometimes trying to get all my projects up to date with newer Drupal core versions, newer PHP versions, newer coding standards, etc. Last week I complained about that I felt like I just completed getting all my projects and sites that I maintain ready for Drupal 10, which took I think about 1.5 years. And now the train starts all over again for Drupal 11.
I sometimes feel that I cannot find the time to work on a new exciting feature that would take over a year build.

But if I take a step back from these stress thoughts, I *could* actually still find time to work on that, it would only probably take 2 years instead of 1 because I need to designate time too for fixing bugs and keeping the project up to date.

It is what it is.

And since this is indeed all voluntary work, technically you indeed do not owe anything to anyone. So thanks for donating your time to Rules and other Drupal projects that you participate in!

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