# Gemfile.lock dependency conflicts

**URL:** <https://meta.discourse.org/t/gemfile-lock-dependency-conflicts/206454>\
**Category:** 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:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![arivanandan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/arivanandan/32/160108_2.png) [@arivanandan](https://meta.discourse.org/u/arivanandan)\
**Post date:** [October 19, 2021, 5:04pm UTC](https://meta.discourse.org/t/gemfile-lock-dependency-conflicts/206454/1 "2021-10-19T17:04:44Z")

</div>

I do not much experience with Ruby so bear with me. I haven’t updated in 2 or 3 months. When I did, there’s a conflict.

[discourse-omniauth-jwt](https://github.com/discourse/discourse-omniauth-jwt/blob/master/discourse-omniauth-jwt.gemspec) needs the jwt gem at 2.2.1

I’m guessing with this [commit](https://github.com/discourse/discourse/commit/bbf96507368f13eb7435169955d1fdd3a8329196#diff-89cade48462044ee1b672dc5f4c3ec250fbd29effcd8932096a23c1283c6731f) to [Gemfile.lock](https://github.com/discourse/discourse/blob/main/Gemfile.lock), discourse now uses version 2.3.0 of jwt.

I’m guessing updating jwt on discourse-omniauth-jwt isn’t really an option since it isn’t updated. What should I do here?

---

<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.

---

<div class="post-metadata">

**Author:** ![arivanandan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/arivanandan/32/160108_2.png) [@arivanandan](https://meta.discourse.org/u/arivanandan)\
**Post date:** [October 20, 2021, 7:51am UTC](https://meta.discourse.org/t/gemfile-lock-dependency-conflicts/206454/4 "2021-10-20T07:51:59Z")

</div>

True. Let me give that a shot.

---

<div class="post-metadata">

**Author:** ![arivanandan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/arivanandan/32/160108_2.png) [@arivanandan](https://meta.discourse.org/u/arivanandan)\
**Post date:** [October 24, 2021, 5:03pm UTC](https://meta.discourse.org/t/gemfile-lock-dependency-conflicts/206454/5 "2021-10-24T17:03:33Z")

</div>

That worked out! I also figured out how to publish my own ruby gem whilst figuring this out.

I see that gems can also be imported with a git URL such as

```plaintext
gem "discourse-omniauth-jwt", "0.0.3", git: "https://github.com/discourse/discourse-omniauth-jwt"

```

Does this not work as a result of how discourse installs dependencies?

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\
**Post date:** [November 23, 2021, 5:04pm UTC](https://meta.discourse.org/t/gemfile-lock-dependency-conflicts/206454/6 "2021-11-23T17:04:10Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.