Closed marcotc closed 2 years ago
Ah, sorry about that! I've released v0.5.1 with 915c2a4 which should restore backwards compatibility with older rubies, and I'll restrict the supported ruby version in the gemspec for the next version.
I can't run older rubies in my local environment, and they don't work on GitHub Actions, so please let me know if it's all working now or not 🙏
@sj26 thank you for the super fast turnaround!
Your changes look good, but they are not reflected in rubygems.org (https://rubygems.org/gems/rspec_junit_formatter/versions/0.5.1):
Did you by any chance upload an older gem build to rubygems?
By the way, I test old Ruby versions with docker: docker run --rm -it ruby:2.1 /bin/sh
.
For this issue, I run gem install rspec_junit_formatter
inside the container.
Sorry I didn’t explain well: I fixed backwards compatibility and released a new version so that the gem will continue to work on old rubies, then I restricted the ruby version for future gem versions so that the same mistake doesn’t creep in. So you should be able to install the current gem version on older rubies and it should run without errors.
Thanks for the Docker tip!
Since https://github.com/sj26/rspec_junit_formatter/releases/tag/v0.5.0, I started getting this error when using
rspec_junit_formatter
with Ruby 2.2.10p489:I noticed that CI only runs for Ruby 2.6+.
If the intention is to drop support for Ruby < 2.6, updating https://github.com/sj26/rspec_junit_formatter/blob/7f69b4f00127563798bb74ab19eeca3fcb5be2d4/rspec_junit_formatter.gemspec#L12 with this requirement will allow older Rubies to continue working. Today,
gem install rspec_junit_formatter
will happily install0.5.0
in older Rubies, but that version will not work.