uninitialized constant DeepL::VERSION in v3.6.1 #17

Activity

1. JanEbbing commented on Dec 29, 2025

   

   JanEbbing

   on Dec 29, 2025

   More actions

   I cannot reproduce this, rails s gives me

   => Booting Puma
   => Rails 8.1.1 application starting in development
   => Run `bin/rails server --help` for more startup options
   Puma starting in single mode...
   * Puma version: 7.1.0 ("Neon Witch")
   * Ruby version: ruby 3.4.8 (2025-12-17 revision 995b59f666) +PRISM [arm64-darwin25]
   *  Min threads: 3
   *  Max threads: 3
   *  Environment: development
   *          PID: 80054
   * Listening on http://127.0.0.1:3000
   * Listening on http://[::1]:3000
   Use Ctrl-C to stop
   

   In your gem installation, do you have the lib/version.rb file which defines DeepL::VERSION? link
2. 341bms commented on Jan 5, 2026

   

   341bms

   on Jan 5, 2026

   Last edited by 341bms

   Author

   More actions

   I use this GEM in several applications, and the problem occurs in all applications in versions from v3.4 onwards. I will check this again in more detail and then get back to you.

   lib/version.rb is present in all local gem installations.
3. fagnerpereira commented on Jan 21, 2026

   

   fagnerpereira

   on Jan 21, 2026

   Last edited by fagnerpereira

   More actions

   @341bms if you are using 3.4 version, try to make sure if the version installed is 3.4.0, because upgrading from version 3.3 all the minor versions 3.4.0, 3.5.0 and 3.6.0 are broken. I tested all of them to be sure.

   To fix that, try to upgrade the last patch versions, so if you are using 3.4.0, them upgrade to 3.4.1. The same for all the next minor updates 3.5 and 3.6. I have just already tested each one as well to make sure those patches upgrades fixed that issue.

   Here is the commit with those fixes: v3.6.0...v3.6.1

   Maybe would be important to clarify this issue in the documentation, to avoid wasting time testing each version to find out which one is broken or not.

   PS: simply running bundle install doesnt guarantee its going to install the latest version, unless you removed the gem from Gemfile run bundle install, add to the Gemfile again and running bundle install. The correct way to make sure that updates to the latest version is by running bundle update deepl-rb, or by freezing the specific version in Gemfile as gem "deepl-rb", "3.6.1" then you can run bundle install normally.
4. jirkamotejl

   added 2 commits that reference this issue on Jan 26, 2026

   fix(deepl_for_traco): pre-load version file before requiring deepl

   ...

   9622902

   fix(deepl_for_traco): pre-load version file before requiring deepl

   ...

   6362348
5. garrettblehm commented on Apr 10, 2026

   

   garrettblehm

   on Apr 10, 2026

   Last edited by garrettblehm

   More actions

   We are still seeing this issue with 3.6.1. The require 'version' is not loading the version correctly because it's resolving to another gem's version.rb.

   I was able to resolve by updating require 'version' to require_relative 'version'.

   It's also worth updating the require 'http_client_options' line as well to require_relative.

   I added a PR to fix #18

   👍React with 👍1Reacted by Richard Young
6. garrettblehm

   added a commit that references this issue on Apr 10, 2026

   update 'require' to 'require_relative' for non deepl/ prefixed files

   ...

   b6ad4ee
7. JanEbbing

   added a commit that references this issue on Apr 13, 2026

   update 'require' to 'require_relative' for non deepl/ prefixed files

   ...

   a6d74df
8. JanEbbing

   closed this as completedin #18on Apr 13, 2026
9. JanEbbing

   reopened this on Apr 13, 2026
10. JanEbbing commented on Apr 13, 2026

    

    JanEbbing

    on Apr 13, 2026

    More actions

    Keeping this open until we release 3.6.2