Skip to content

chore(deps): bump vulnerable gems in Gemfile.lock - #47

Merged
whoseoyster merged 1 commit into
mainfrom
rishab/open-13164-upgrade-vulnerable-dependencies-in-the-sdks-and-public
Oct 15, 2026
Merged

whoseoyster merged 1 commit into
mainfrom
rishab/open-13164-upgrade-vulnerable-dependencies-in-the-sdks-and-public

Conversation

@whoseoyster

Copy link
Copy Markdown
Contributor

Summary

Conservative bundle update of gems in Gemfile.lock that have published advisories. All are development/test/docs dependencies (the gem's runtime deps, cgi and connection_pool, are unchanged). No generated code is touched.

Changes

  • addressable 2.8.7 -> 2.9.0 (high)
  • concurrent-ruby 1.3.5 -> 1.3.8 (high)
  • json 2.15.2 -> 2.21.2 (high)
  • activesupport 8.1.1 -> 8.1.4 and yard 0.9.37 -> 0.9.45 (moderate)
  • The lockfile's openlayer PATH spec moves from 0.16.0 to 0.17.0; bundler syncs this to lib/openlayer/version.rb automatically (it was stale after the last release).

Command: bundle _2.4.1_ update --conservative addressable concurrent-ruby json activesupport yard (Ruby 3.2).

Testing

  • bundle exec rake test against the local mock server (Ruby 3.2 in Docker): 143 runs, 0 failures, 0 errors
  • osv-scanner scan source -r .: 11 advisories before, none after

Residual advisories

None reported by osv-scanner.

Risk / rollout

Dev tooling only; the published gem's dependency set is unchanged. Nothing to do at release.

Part of OPEN-13164 (one PR per repo, so this does not close the ticket on its own)

馃 Generated with Claude Code

Conservative bundle update of addressable, concurrent-ruby, json,
activesupport and yard to patched releases. Also syncs the lockfile's
openlayer path spec to the current gem version.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@whoseoyster
whoseoyster merged commit b2a61d3 into main Oct 15, 2026
8 checks passed
@whoseoyster
whoseoyster deleted the rishab/open-13164-upgrade-vulnerable-dependencies-in-the-sdks-and-public branch October 15, 2026 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants