Skip to content

fix: Remove bundler version constraint from gemspec#20

Merged
jsonbailey merged 1 commit intomainfrom
devin/1771858629-fix-bundler-constraint
Feb 23, 2026
Merged

fix: Remove bundler version constraint from gemspec#20
jsonbailey merged 1 commit intomainfrom
devin/1771858629-fix-bundler-constraint

Conversation

@jsonbailey
Copy link
Contributor

Requirements

  • I have added test coverage for new or changed functionality
  • I have followed the repository's pull request submission guidelines
  • I have validated my changes against all supported platform versions

No test changes needed — this is a dependency metadata fix only.

Related issues

Fixes Windows CI build failure: https://github.com/launchdarkly/ruby-server-sdk-ai/actions/runs/22231968538/job/64313766966

Describe the solution you've provided

The gemspec declared bundler ~> 2.0 as a development dependency, which constrains Bundler to >= 2.0, < 3.0. The Windows CI runner now ships with Bundler 4.0.6, causing bundle install to fail with a version conflict.

This PR removes the bundler development dependency entirely. Bundler is part of the Ruby toolchain and does not need to be listed as a gem dependency — it is always available in any Ruby environment.

Describe alternatives you've considered

  • Relaxing the constraint (e.g., >= 2.0): This would work but is unnecessary since bundler doesn't need to be declared as a dependency at all.
  • Pinning a bundler version in CI: This would paper over the issue and require ongoing maintenance as runner images change.

Human review checklist

  • Confirm removing the bundler constraint (rather than relaxing it) is acceptable
  • Verify no other files (e.g., Gemfile, CI workflows) rely on this constraint being present

Additional context

Link to Devin run | Requested by @jsonbailey

The gemspec specified 'bundler ~> 2.0' as a development dependency, which
is incompatible with Bundler 4.x now shipping with newer Ruby/OS images.
Bundler is part of the Ruby toolchain and does not need to be constrained
as a gem dependency.

Co-Authored-By: unknown <>
@devin-ai-integration
Copy link

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@jsonbailey jsonbailey merged commit ef18f32 into main Feb 23, 2026
9 checks passed
@jsonbailey jsonbailey deleted the devin/1771858629-fix-bundler-constraint branch February 23, 2026 20:48
jsonbailey added a commit that referenced this pull request Feb 25, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.2.2](0.2.1...0.2.2)
(2026-02-25)


### Bug Fixes

* Improve usage reporting
([#18](#18))
([9f7ec17](9f7ec17))
* Remove bundler version constraint from gemspec
([#20](#20))
([ef18f32](ef18f32))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Jason Bailey <jbailey@launchdarkly.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants