ruby/rubygems · error

[DEPRECATED] #{message}

Error message

[DEPRECATED] #{message}

What it means

Error "[DEPRECATED] #{message}" thrown in ruby/rubygems.

Source

Thrown at lib/bundler/shared_helpers.rb:133

      raise VirtualProtocolError.new
    rescue Errno::ENOSPC
      raise NoSpaceOnDeviceError.new(path, action)
    rescue Errno::ENOTSUP
      raise OperationNotSupportedError.new(path, action)
    rescue Errno::EPERM
      raise OperationNotPermittedError.new(path, action)
    rescue Errno::EROFS
      raise ReadOnlyFileSystemError.new(path, action)
    rescue Errno::EEXIST, Errno::ENOENT
      raise
    rescue SystemCallError => e
      raise GenericSystemCallError.new(e, "There was an error #{[:create, :write].include?(action) ? "creating" : "accessing"} `#{path}`.")
    end

    def feature_deprecated!(message)
      return unless prints_major_deprecations?

      Bundler.ui.warn("[DEPRECATED] #{message}")
    end

    def feature_removed!(message)
      require_relative "errors"
      raise RemovedError, "[REMOVED] #{message}"
    end

    def print_major_deprecations!
      multiple_gemfiles = search_up(".") do |dir|
        gemfiles = gemfile_names.select {|gf| File.file? File.expand_path(gf, dir) }
        next if gemfiles.empty?
        break gemfiles.size != 1
      end
      return unless multiple_gemfiles
      message = "Multiple gemfiles (gems.rb and Gemfile) detected. " \
                "Make sure you remove Gemfile and Gemfile.lock since bundler is ignoring them in favor of gems.rb and gems.locked."
      Bundler.ui.warn message
    end

View on GitHub (pinned to 86cbb817a3)

Solutions

1. Stop using the deprecated feature named in the message and migrate to its documented replacement

When it happens

Trigger: Thrown at lib/bundler/shared_helpers.rb:133 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of ruby/rubygems@86cbb817a3 (2026-08-23). Data as JSON: /api/errors/86dcee3c42e66617. Report an issue: GitHub.