# Gemfile.lock dependency conflicts

**URL:** <https://meta.discourse.org/t/gemfile-lock-dependency-conflicts/206454>\
**Category:** Product Support\
**Created:** [October 19, 2021, 5:04pm UTC](https://meta.discourse.org/t/gemfile-lock-dependency-conflicts/206454 "2021-10-19T17:04:44Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Benjamin\_D](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/benjamin_d/32/277831_2.png) [@Benjamin\_D](https://meta.discourse.org/u/Benjamin_D)\
**Post date:** [October 19, 2021, 6:38pm UTC](https://meta.discourse.org/t/gemfile-lock-dependency-conflicts/206454/3 "2021-10-19T18:38:14Z")

</div>

> [@arivanandan](#):
>
> I’m guessing updating jwt on discourse-omniauth-jwt isn’t really an option since it isn’t updated. What should I do here?

I’d try my luck, fork it and bump the dependency to 2.3.0  
From what I can tell [what motivated the 2.2.1](https://github.com/discourse/discourse-omniauth-jwt/commit/c7bf8df33762faab9ff4e1989decb6d50179ae19) (which was the latest at the time of the commit in 2019) has not changed.

---

_[View the full topic](https://meta.discourse.org/t/gemfile-lock-dependency-conflicts/206454)._