Next steps on token handling?
When Email API 2.5 was released, I didn't update my sites, because I knew that Civi 5.43 was overhauling tokens, and I wanted to not test tokens twice.
In my testing, I found that 5.43 didn't change token handling, but Email API 2.5 did break contribution tokens with 5.42 and 5.43 for me, whereas Email API 2.4 continues to work for me.
I understand that there have been issues, but I think most users of the extension would agree that support of non-contact tokens (especially contribution tokens) is important functionality, so I'm wondering what the next steps should be.
Given the TokenProcessor work in Civi 5.43, perhaps Email API 3.0 should be released, with support for 5.43 only, and 2.x can continue to receive updates until it's no longer necessary? We have a precedent in Email API 1.x, which also received updated after 2.0 was released.