chore: update LaunchDarkly SDKs and gem lockfile to latest within-major - #92
Merged
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
Author
|
@cursor review |
kinyoklion
marked this pull request as ready for review
August 31, 2026 22:54
keelerm84
approved these changes
Sep 1, 2026
jsonbailey
approved these changes
Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Routine dependency refresh for the example: both LaunchDarkly SDKs (Ruby server + browser) and the committed gem lockfile move to the latest versions within their current majors.
Gemfile.lock:launchdarkly-server-sdk8.15.0 → 8.15.1 (plus the otherbundle updateresolutions: rack 3.2.7, rbs 4.2.0, reline 0.7.0, selenium-webdriver 4.48.0, sprockets 4.4.1, etc.)config/importmap.rb:@launchdarkly/js-client-sdkpin 4.9.4 → 4.10.0~> 8.10already permits 8.15.1, and the Ruby version pin (3.3.1) is unchangedImplementation details
Verified by running the app in a
ruby:3.3.1container against the hello-apps environment (server SDK key + client-side ID via env vars, never committed):bundle install,bin/rails db:migrate,bin/rails test→ 1 run, 1 assertion, 0 failuresbin/rails serverand loadinglocalhost:3000in Chrome: both the normal and the bootstrapped browser client render{ "hello-boolean": true }, so the bootstrap path works with js-client-sdk 4.10.0db/schema.rbRails-version-header rewrite produced bydb:migratewas reverted so it isn't part of this diffNo open PRs existed on this repo at the time of this change (last run's #90/#91 are closed/merged).
Link to Devin session: https://app.devin.ai/sessions/dbae57d29dc44ef5adc0afe082345bfa
Open in Devin Desktop: https://app.devin.ai/desktop/session/dbae57d29dc44ef5adc0afe082345bfa?variant=devin
Note
Overview
Bumps LaunchDarkly dependencies without changing
Gemfileconstraints: the Ruby server SDK inGemfile.lockmoves 8.15.0 → 8.15.1, and the browser client CDN pin inconfig/importmap.rbmoves @launchdarkly/js-client-sdk 4.9.4 → 4.10.0.The lockfile also picks up incidental
bundle updateresolutions (e.g. rack 3.2.7, sprockets 4.4.1, selenium-webdriver 4.48.0, reline 0.7.0, rbs 4.2.0, and other transitive gems). No application Ruby or JavaScript source files are modified in this diff.Reviewed by Cursor Bugbot for commit 110d7db. Bugbot is set up for automated code reviews on this repo. Configure here.