Skip to main content

Ruby pre release gem

Hi there, my team is working on the upgrade to Mindee V2 for a Ruby on Rails application. We’re currently using version 4.6.0 but are having issues with upgrading to version 4.7.0.pre.rc2, getting the following error in the console:


bin/rails aborted!

/opt/homebrew/lib/ruby/gems/3.3.0/gems/mindee-4.7.0.pre.rc1/lib/mindee/http/api_settings_v2.rb:23:in `<class:ApiSettingsV2>': uninitialized constant Mindee::VERSION (NameError)

USER_AGENT = "mindee-api-ruby@v#{Mindee::VERSION} ruby-v#{RUBY_VERSION} #{Mindee::PLATFORM}".freeze ^^^^^^^^^

Did you mean? VersionGem

Is there any additional config we need to do/is anyone else having similar issues. With v1 becoming end of life very soon we’re keen to get this migration as seamless as possible.

Status: Completed6 comments

Log in to comment and vote

Comments6

  • Sebastian Olivera Silvera

    •

    Aug 29, 2025

    Hello Freya,

    The error you indicated shows that the version number is improperly imported in our API settings module. A fix is on the way.

    I am however curious as to why any of our tests didn’t catch this error until now.
    Would you mind sharing the following information to help us narrow the problem down?

    • I assume from the logs you are using macOS, is this correct?

    • The logs seem to point at the rc1, not the rc2 like you mentioned above. Is this normal?

    • Can you share a minimal snippet of the file you use to call Mindee in your code?

    • Does Rails load the gem with any specific parameters?

    I will notify you when a new version is available with a bug fix.

    Best,

    Sebastian

    • Sebastian Olivera Silvera

      •

      Aug 29, 2025

      Update: the gem with the fix has been published.

  • Ianaré Sévi

    Team•

    Aug 29, 2025

    Hi, thanks for your report.

    We’re currently investigating and will get back to you as soon as we have some information.

  • Freya Dixon

    •

    Aug 29, 2025

    Also apologies meant to tag this as a bug report/question rather than a feature request