Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: crmne/ruby_llm
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1.14.0
Choose a base ref
...
head repository: crmne/ruby_llm
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.14.1
Choose a head ref
  • 9 commits
  • 524 files changed
  • 4 contributors

Commits on Mar 17, 2026

  1. Configuration menu
    Copy the full SHA
    f63c65a View commit details
    Browse the repository at this point in the history
  2. Fix ActiveStorage::Blob re-upload if used in with: param (#683)

    ## What this does
    
    Fixes #665
    
    When an `ActiveStorage::Blob` is passed to `ask` or
    `create_user_message` via `with:`, it is downloaded and re-uploaded as a
    new blob. This is because the blob gets wrapped in a
    `RubyLLM::Attachment` during content building, so it goes to the `else`
    branch in `prepare_for_active_storage` and
    `convert_to_active_storage_format` is called, which always creates a new
    IO hash.
    
    => Fix by updating `convert_to_active_storage_format` to detect
    `ActiveStorage` objects and return it directly so it can be reused.
    
    ## Type of change
    
    - [x] Bug fix
    - [ ] New feature
    - [ ] Breaking change
    - [ ] Documentation
    - [ ] Performance improvement
    
    ## Scope check
    
    - [x] I read the [Contributing
    Guide](https://github.com/crmne/ruby_llm/blob/main/CONTRIBUTING.md)
    - [x] This aligns with RubyLLM's focus on **LLM communication**
    - [x] This isn't application-specific logic that belongs in user code
    - [x] This benefits most users, not just my specific use case
    
    ## Quality check
    
    - [x] I ran `overcommit --install` and all hooks pass
    - [x] I tested my changes thoroughly
    - [ ] For provider changes: Re-recorded VCR cassettes with `bundle exec
    rake vcr:record[provider_name]`
      - [x] All tests pass: `bundle exec rspec`
    - [ ] I updated documentation if needed
    - [x] I didn't modify auto-generated files manually (`models.json`,
    `aliases.json`)
    
    ## AI-generated code
    
    - [x] I used AI tools to help write this code
    - [x] I have reviewed and understand all generated code (required if
    above is checked)
    
    ## API changes
    
    - [ ] Breaking change
    - [ ] New public methods/classes
    - [ ] Changed method signatures
    - [x] No API changes
    
    Co-authored-by: nebel95 <nebel95@wallwisher.com>
    Co-authored-by: Carmine Paolino <carmine@paolino.me>
    3 people authored Mar 17, 2026
    Configuration menu
    Copy the full SHA
    61bccb4 View commit details
    Browse the repository at this point in the history

Commits on Mar 23, 2026

  1. Update moderation.md (#703)

    Title for Integration Patterns was incorrect since Patterns was spelled
    as Patters
    
    ## What this does
    
    Simple spelling mistake fix.
    
    ## Type of change
    
    - [ ] Bug fix
    - [ ] New feature
    - [ ] Breaking change
    - [x] Documentation
    - [ ] Performance improvement
    
    ## Scope check
    
    - [x] I read the [Contributing
    Guide](https://github.com/crmne/ruby_llm/blob/main/CONTRIBUTING.md)
    - [x] This aligns with RubyLLM's focus on **LLM communication**
    - [x] This isn't application-specific logic that belongs in user code
    - [x] This benefits most users, not just my specific use case
    artinboghosian authored Mar 23, 2026
    Configuration menu
    Copy the full SHA
    3c6e53c View commit details
    Browse the repository at this point in the history

Commits on Mar 27, 2026

  1. Updated plausible script

    crmne committed Mar 27, 2026
    Configuration menu
    Copy the full SHA
    5c28730 View commit details
    Browse the repository at this point in the history

Commits on Mar 30, 2026

  1. fixed plausible snippet

    crmne committed Mar 30, 2026
    Configuration menu
    Copy the full SHA
    aae030c View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    4ed9dfb View commit details
    Browse the repository at this point in the history

Commits on Apr 2, 2026

  1. Configuration menu
    Copy the full SHA
    070f5a0 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    33c20c8 View commit details
    Browse the repository at this point in the history
  3. Bump to 1.14.1

    crmne committed Apr 2, 2026
    Configuration menu
    Copy the full SHA
    ac4d5d7 View commit details
    Browse the repository at this point in the history
Loading