Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ruby/ruby@596db9c #963

Closed
iliabylich opened this issue Dec 25, 2023 · 3 comments · Fixed by #1010
Closed

ruby/ruby@596db9c #963

iliabylich opened this issue Dec 25, 2023 · 3 comments · Fixed by #1010
Labels

Comments

@iliabylich
Copy link
Collaborator

ruby/ruby@596db9c

@Earlopain
Copy link
Contributor

This has been backported to 3.3 in ruby/ruby@2a84aaf (don't mind the wrong commit title)

@iliabylich
Copy link
Collaborator Author

It's been a while since Ruby devs made grammar changes in patch version bumps and I actually thought they started following SemVer 😄.

Thanks, noted. The next release of parser must have this change in ruby33.y

@Earlopain
Copy link
Contributor

This thing is pretty unfortunate in that the bug has been introduced after the last 3.3 preview was released. I'm just glad that finally a new patch version was made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants