BTW, is it necessary to update the ChangeLog for TruffleRuby releases? This would remain as a manual step as there is no easy way to predict the PR number.

@pkuczynski Could you merge this PR?

On the question of where to put it, I wonder if it'd be worth keeping it top level but renaming it update-versions.sh with just a truffleruby argument for now? (Similar to ruby-versions' update.sh.)

I'm not looking forward to generalize the script for all Ruby implementations at this time, I'd rather merge what works and is useful now.

I could rename to update-versions.rb and only support truffleruby, but that seems slightly misleading for me.

@havenwood @pkuczynski Please tell me what changes you want before merging, and then let's merge it 😃

Since it's an internal, contributor-facing script I think we can merge it as-is, then move it to update-versions.rb truffleruby once we have another engine's update script to add.

Thank you for the PR!

Thanks for merging!

Sorry, was on holiday...

@pkuczynski No worry. I wanted to merge this soon as it allows to simplify these instructions quite a bit:
truffleruby/truffleruby@1217310?short_path=7400bc7 (and of course makes it much easier to update TruffleRuby in RVM).