[BUG] v1.5.0 breaking change in capabilities from Array to Hash ???

[MadBomber]

Basic checks

• I searched existing issues - this hasn't been reported
• I can reproduce this consistently
• This is a RubyLLM bug, not my application code

What's broken?

There may be a breaking change in v1.5.0 which has a Hash object for the model's capabilities object. In previous versions this object was an Array.

My aia gem with the directive for available_models produces a report for v1.4.0 and v1.3.1 but when v1.5.0 is used it throws an exception telling me that I can't use a join on capabilities because its a Hash.

However, if I go into IRB the object is showing as the expected Array:

irb(main):012:0> RubyLLM::VERSION
"1.5.0"
irb(main):013:0> llm.class
RubyLLM::Chat
irb(main):014:0> llm.model.capabilities
["batch", "function_calling", "structured_output"]

So I'm still puzzled as to whether this is a RubyLLM problem (leaning that way because AIA does not throw the exception on versions prior to 1.5.0) This may be associated with the new models that have been added to RubyLLM. Will know more after I dig a little deeper.

BTW i like your issue template.

How to reproduce

config with standard stuff
chat.model.capabilities

Expected behavior

expected Array got a Hash

What actually happened

expected Array got a Hash

Environment

3.4.5
1.5.0
MacOS

[MadBomber]

I was right. Its a model data inconsistency with the new mistral models ...

2025-07-31 22:34:11.708609 DEBUG Source:  /Users/dewayne/sandbox/git_repos/madbomber/aia/develop/lib/aia/directive_processor.rb:362:in 'block in AIA::DirectiveProcessor#available_models'
2025-07-31 22:34:11.708609 DEBUG llm -=> #<RubyLLM::Model::Info:0x00000001216ba798
 @capabilities=
  {chat: true, streaming: true, tools: true, vision: false, json_mode: true},
 @context_window=32768,
 @created_at="2024-11-26 00:00:00 +0100",
 @family="codestral",
 @id="codestral-2411-rc5",
 @knowledge_cutoff=nil,
 @max_output_tokens=8192,
 @metadata={object: "model", owned_by: "mistralai"},
 @modalities=
  #<RubyLLM::Model::Modalities:0x0000000121e19bb0
   @input=["text"],
   @output=["text"]>,
 @name="Codestral",
 @#=#<RubyLLM::Model::#:0x0000000121e19b38 @data={}>,
 @provider="mistral">
2025-07-31 22:34:11.708609 DEBUG llm.capabilities -=> {chat: true, streaming: true, tools: true, vision: false, json_mode: true}

[crmne]

Thanks for reporting this. That definitely needed more time in the oven. I'm working on a fix that will include a JSON schema and will validate the resulting models.json against it.

[crmne]

Fixed and cut a new version: 1.5.1!