The splitting out of Python state is cool and all, and make sense.

It had one undocumented side-effect that bit me: previously, state would grab the GhidraState state member from GhidraScript directly and let me access the state that you.

It can be substituted by getState(), which is the Ghidra provided API for it, I suppose. I had to learn that the hard way because, until now, I'd never actually needed to use the API. (Jython provides the same direct access to that variable.)

It may be worth a late-breaking addition to your release notes to save the next person who runs into this the same confusion. (or not, but I figured I'd mention it.)

PS: on the plus side, they upgrade saved a bug report about an interpreter crash that has been fixed along the way, so good work there.