Hi,
On 11/29/22 12:49, Isabelle Hurbain-Palatin wrote:
As part of the effort to align Parsoid's output
with the output of the
legacy parser [1], we're introducing a backwards incompatible change [2]
in the next Parsoid version (0.17.0-a7, to be deployed along with
1.40.0-wmf.12).
Given that this is this week's train that's already in progress, it's
really not enough time to update code that is expecting the old format.
Can this be delayed a bit?
[5] This would technically have required a major bump
in the
specification version. Since we don't have a well-tested implementation
for content negotiation and the RESTBase sunsetting work is in progress
[6], bumping major versions wasn't an option.We overlooked bumping a
minor version as a signal, because we assumed we had it covered in 2.6.0.
Is there something blocking a bump to 2.7.0 now? I don't understand why
it's being retconned into 2.6.0.
-- Kunal / Legoktm