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 needs the jwt gem at 2.2.1 I’m guessing with this commit to 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?

[image] 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 (which was the latest at the time of the commit in 2019) has not changed.

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

Gemfile.lock dependency conflicts

Product Support

arivanandan (Arivanandan) October 20, 2021, 7:51am 4

True. Let me give that a shot.

Topic		Replies	Views
Using "custom" ruby gems Development	5	1242	April 28, 2022
Installing a git-based gem from a discourse plugin Development	4	905	September 11, 2022
Error upgrading Discourse - gem conflict Self-hosting	8	1299	June 5, 2020
Webpush gem is not latest Development	5	730	May 8, 2018
Upgrade to 3.0.2: NameError: undefined method `call' for class `Redis::Client' (with a "fix") Self-hosting unsupported-install	11	2557	June 23, 2023

Gemfile.lock dependency conflicts

Related topics