chore: resolve open dependabot security alerts#180
Conversation
github-actions
Bot
assigned
dabeeeenster,
josecolella,
matthewelwell,
maxveldink,
thomaspoignant and
Zaimwa9
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates several dependency versions across multiple Gemfile.lock files for various OpenFeature providers, including openfeature-flagsmith-provider, openfeature-go-feature-flag-provider, openfeature-meta_provider, and openfeature-ofrep-provider. Specifically, it bumps versions for dependencies such as addressable, faraday, faraday-net_http, json, and public_suffix. There are no review comments, and I have no feedback to provide.
2731d8d to
05604d0
Compare
05604d0 to
7d0904b
Compare
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
86882d7 to
28233e4
Compare
|
Warning Review limit reached
Next review available in: 40 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
d6bf75d to
90c8919
Compare
Pull request was converted to draft
Signed-off-by: Jonathan Norris <jonathan.norris@dynatrace.com>
- faraday 2.14.2 -> 2.14.3 (high, alert #47) in openfeature-go-feature-flag-provider - faraday 2.14.2 -> 2.14.3 (high, alert #46) in openfeature-ofrep-provider - faraday 2.14.2 -> 2.14.3 (high, alert #45) in openfeature-flagsmith-provider Signed-off-by: Jonathan Norris <jonathan.norris@dynatrace.com>
The Gemfile requires simplecov ~> 1.0 (bumped in #193) but the gemspec's dev dependency was still pinned to ~> 0.22, and Gemfile.lock still resolved simplecov 0.22.0. This conflict makes bundler >= 2.7 refuse to parse the Gemfile, which would break CI on this branch after rebasing onto main. Aligning the gemspec constraint and regenerating the lock resolves the conflict. Signed-off-by: Jonathan Norris <jonathan.norris@dynatrace.com>
90c8919 to
cf77c27
Compare
Summary
simplecovgemspec/Gemfileversion conflict inopenfeature-flagsmith-provider(unrelated to Dependabot, but needed sobundle installdoesn't fail on this branch after rebasing ontomain).Dependabot Alerts Resolved
faradayproviders/openfeature-go-feature-flag-provider/Gemfile.lockfaradayproviders/openfeature-ofrep-provider/Gemfile.lockfaradayproviders/openfeature-flagsmith-provider/Gemfile.lockfaradayproviders/openfeature-go-feature-flag-provider/Gemfile.lockfaradayproviders/openfeature-ofrep-provider/Gemfile.lockfaradayproviders/openfeature-flagsmith-provider/Gemfile.lockaddressableproviders/openfeature-flagsmith-provider/Gemfile.lockaddressableproviders/openfeature-go-feature-flag-provider/Gemfile.lockjsonproviders/openfeature-meta_provider/Gemfile.lockVerification
bundle exec rspecandbundle exec rubocoppass on each affected provider: go-feature-flag (82 examples), ofrep (44 examples), flagsmith (89 examples), meta_provider (58 examples).