syntax error after update version 3.4.0

[yalanin]

Hello：
Our Project raise syntax error after update version 3.4.0 today, the following is the error message it has showed:

/mime-types-3.4.0/lib/mime/types/cache.rb:26: syntax error, unexpected tIDENTIFIER, expecting '(' (SyntaxError)
Could not load MIME::Types cache: invalid version
/mime-types-3.4.0/lib/mime/types/cache.rb:32: syntax error, unexpected tIDENTIFIER, expecting '('
Could not load MIME::Types cache: #{e}

We try to add " in line 26 and 32 in cache.rb:

MIME::Types.logger.warn <<~WARNING.chomp
    "Could not load MIME::Types cache: invalid version"
WARNING

MIME::Types.logger.warn <<~WARNING.chomp
   "Could not load MIME::Types cache: #{e}"
WARNING

and it appear another error:

/mime/types/registry.rb:49: syntax error, unexpected tIDENTIFIER, expecting keyword_end (SyntaxError)
($RUBY_MIME_TYPES_LAZY_LOAD) is deprecated and will be remov...

and so do we to registry.rb in line 49, it works:

MIME::Types.logger.warn <<~WARNING.chomp
   "Lazy loading ($RUBY_MIME_TYPES_LAZY_LOAD) is deprecated and will be removed."
WARNING

we are not sure this is right way to fix the error or not, could you please help us confirm this issue? Thank You!

Best Regard!

[electrofelix]

Looks to me like release 3.4.0 is using syntax that is not supported by ruby < 2.3?

https://github.com/vagrant-libvirt/vagrant-libvirt/runs/4217516069?check_suite_focus=true

Rather than try to fix the syntax, should https://github.com/mime-types/ruby-mime-types/blob/main/mime-types.gemspec#L20 be updated to reference 2.3 as the minimum version rather than 2.0? Assuming it's possible do a bugfix release and yank 3.4.0 so that installs on older rubies for some older distros will ignore the more recent releases?

While 2.2 is no longer supported for security fixes by the security developers, ruby 2.0 is in centos 7 which has security updates until 2024.

[halostatue]

I will do a bug fix release with this. I won’t be yanking 3.4.0 (for reasons), but this should be quickly addressable.

[halostatue]

mime-types 3.4.1 has been released and should fix this. Please advise if it does not.