[dependabot]

Bumps ruby_llm from 2.1.0 to 2.1.1.

Release notes

Sourced from ruby_llm's releases.

RubyLLM 2.1.1 fixes fresh installs that today's faraday-net_http 3.5.0 release broke, connects to MCP servers that predate the 2026-07-28 revision, and keeps batch embeddings paired with the right inputs.

bundle add ruby_llm --version 2.1.1

Already on 2.1? Run bundle update ruby_llm. No schema or code changes are needed.

Fixed

• Install RubyLLM with the latest faraday-net_http. faraday-net_http 3.5.0 falls outside the range every Faraday from 2.0.1 to 2.14.4 accepts, so a fresh bundle install resolved Faraday 2.0.0, which loads no default adapter, and every request failed with :net_http is not registered on Faraday::Adapter. RubyLLM now excludes Faraday 2.0.0. By @​crmne; thanks @​juneira. (ef2bebdb)
• Connect to MCP servers that predate the 2026-07-28 revision. A server that rejects the revision with -32022 now gets the initialize handshake whether it lists the legacy revisions it speaks, as Atlassian's does, or lists none, as Datadog's does. By @​ebeigarts, @​juneira, and @​crmne. (#1056, #1057, #1053, #1055)
• Pair batch embeddings with the right inputs. OpenAI-compatible and Mistral batch results now place each vector by the position the provider reports, and mark a result with duplicate, missing, or out-of-range positions as failed instead of pairing its vectors with the wrong texts. By @​D41910. (#1051, #1052)
• Keep the Bedrock inference profile you choose. An id that already names a geography, such as eu.anthropic.claude-sonnet-5-5, is no longer rewritten to another region's profile, so requests stay where your IAM policy allows them. By @​s-andringa. (#1050)
• Keep chat replies when a usage row cannot be linked. A persisted chat saves the reply and logs the failed link, instead of rolling back an answer the provider already billed. By @​yorzi. (#1048, #1049)
• Upload converted attachments again after a provider deletes them. The chat forgets the stale upload and retries, as it already did for plain attachments. By @​yorzi. (#1046, #1047)

Thanks

Thanks to @​yorzi, @​s-andringa, @​D41910, @​ebeigarts, and @​juneira for the fixes and reports in this release.

Full changelog: crmne/ruby_llm@v2.1.0...v2.1.1

Changelog

Sourced from ruby_llm's changelog.

RubyLLM 2.1.1 fixes fresh installs that today's faraday-net_http 3.5.0 release broke, connects to MCP servers that predate the 2026-07-28 revision, and keeps batch embeddings paired with the right inputs.

bundle add ruby_llm --version 2.1.1

Already on 2.1? Run bundle update ruby_llm. No schema or code changes are needed.

Fixed

• Install RubyLLM with the latest faraday-net_http. faraday-net_http 3.5.0 falls outside the range every Faraday from 2.0.1 to 2.14.4 accepts, so a fresh bundle install resolved Faraday 2.0.0, which loads no default adapter, and every request failed with :net_http is not registered on Faraday::Adapter. RubyLLM now excludes Faraday 2.0.0. By @​crmne; thanks @​juneira. (ef2bebdb)
• Connect to MCP servers that predate the 2026-07-28 revision. A server that rejects the revision with -32022 now gets the initialize handshake whether it lists the legacy revisions it speaks, as Atlassian's does, or lists none, as Datadog's does. By @​ebeigarts, @​juneira, and @​crmne. (#1056, #1057, #1053, #1055)
• Pair batch embeddings with the right inputs. OpenAI-compatible and Mistral batch results now place each vector by the position the provider reports, and mark a result with duplicate, missing, or out-of-range positions as failed instead of pairing its vectors with the wrong texts. By @​D41910. (#1051, #1052)
• Keep the Bedrock inference profile you choose. An id that already names a geography, such as eu.anthropic.claude-sonnet-5-5, is no longer rewritten to another region's profile, so requests stay where your IAM policy allows them. By @​s-andringa. (#1050)
• Keep chat replies when a usage row cannot be linked. A persisted chat saves the reply and logs the failed link, instead of rolling back an answer the provider already billed. By @​yorzi. (#1048, #1049)
• Upload converted attachments again after a provider deletes them. The chat forgets the stale upload and retries, as it already did for plain attachments. By @​yorzi. (#1046, #1047)

Thanks

Thanks to @​yorzi, @​s-andringa, @​D41910, @​ebeigarts, and @​juneira for the fixes and reports in this release.

Full changelog: crmne/ruby_llm@v2.1.0...v2.1.1

Commits

• a40182d Prepare RubyLLM 2.1.1 for release
• e5a7a42 MCP: shake hands when a version reject lists nothing
• a8c17eb Check the Faraday 2.0.0 exclusion under the v1 job too
• ef2bebd Exclude Faraday 2.0.0, which has no default adapter
• e9dcd62 MCP: fall back to the handshake when a version reject lists a legacy revision...
• fa28fe3 Check Mistral batch embedding row positions before pairing vectors with input...
• 5556592 Check embedding batch row positions before pairing vectors with inputs (#1051)
• a67da2c Keep Bedrock ids that already name an inference profile (#1050)
• 93e2179 Keep chat replies when a usage row cannot be linked (#1049)
• 661f3d8 Restore uploads for converted attachments (#1047)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)