As some of you have noticed, the SaxonJS “no longer supported” bug returned a few days ago. I’d have sworn that I removed that warning when we shipped SaxonJS 2.6. But I’d also have sworn we would get 3.0 out before now. Maybe I’m not very good at swearing.
That warning has been removed from SaxonJS 2.7, so this issue won’t surface again next October.
Apologies for not getting a maintenance release out sooner. We really should have. Focus has been on SaxonJS 3.0, which is still coming along nicely, but there were a number of bug fixes in SaxonJS 2.x that we could have shipped months ago.
My expectation is that we’ll ship some sort of beta test version of SaxonJS 3.0 “real soon now” and Saxon 12.6 to fix the SEF bug in 12.5 shortly before or after that.