Requesting new release

[mbj]

Hi Prism Team,

I'm the unparser maintainer/author and would like to kindly request a new release from main so I can release unparser with prism as backend (using the translation layer). This would unblock unparser 3.4 support.

There are 2 important, currently unreleased, bugfixes as prism backed unparser will depend upon:

https://github.com/ruby/prism/pull/3540 https://github.com/ruby/prism/pull/3508

Why is this request important?

Unparser has a big userbase, and currently cannot do 3.4 correctly as parser is not perfectly 3.4 capable.

References:

• Unparser PR to support 3.4 via prism: https://github.com/mbj/unparser/pull/387
• Unparser issue about 3.4: https://github.com/mbj/unparser/issues/385

Big shout out to @viralpraxis who did all the heavly lifting here, I'm just the messanger for this request.

Kind regards,

Markus

[viralpraxis]

Just want to note that the first bug (https://github.com/ruby/prism/pull/3540) also affects RuboCop, for instance see https://github.com/rubocop/rubocop/pull/14103

[Earlopain]

I am also requesting a new release. Appart from the issues linked above, there are other problems that are now fixed that were reported againast RuboCop.

It has been about 6 months since the last release. Since then patch versions of ruby had syntax fixes which are not released for the gem, so it still parses as some older patch version. And it looks like ruby itself is now also requesting a new release from the linked PR above.

[kddnewton]

v1.5.0 is released.