v2.5.33 backwards-breaks packages depending on it, including current github.com/tdewolff/minify/v2 about parse

[tdewolff]

Ah yeah keep forgetting that. The new release of minify should fix this.

[wolfbyteit]

I dont think that's the best option here - what about people that were using github.com/tdewolff/parse/v2 and depend on OptChainExpr in their code? They would have to use v2.5.32 and can never update their dependencies anymore because go doesnt allow fixing minor verison numbers (since there is no need for that in semantic versioning).

The go toolchain has a solution for this exact problem: revert the release (see https://play-with-go.dev/retract-module-versions_go116_en/), mark OptCharExpr as deprecated using a deprecation doc comment and delay removing it until v3.0.0.