# Webpush gem 并非最新版本

**URL:** <https://meta.discourse.org/t/webpush-gem-is-not-latest/86829>\
**Category:** Development\
**Created:** [2018年五月5日 13:22 UTC](https://meta.discourse.org/t/webpush-gem-is-not-latest/86829 "2018-05-05T13:22:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![darix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darix/32/114280_2.png) [@darix](https://meta.discourse.org/u/darix)\
**Post date:** [2018年五月5日 13:22 UTC](https://meta.discourse.org/t/webpush-gem-is-not-latest/86829/1 "2018-05-05T13:22:13Z")

</div>

any reason for this?

---

<div class="post-metadata">

**Author:** ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)\
**Post date:** [2018年五月5日 15:35 UTC](https://meta.discourse.org/t/webpush-gem-is-not-latest/86829/2 "2018-05-05T15:35:41Z")

</div>

it’s a dependency that was working in the plugin when we migrated. There appears to have been some issues in the past with those libs sometimes breaking and not sending notifications. I wanted no chance of that happening while I was porting, so I used dependencies I knew were working.

What does that particular patch give you that you’re missing?

---

<div class="post-metadata">

**Author:** ![darix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darix/32/114280_2.png) [@darix](https://meta.discourse.org/u/darix)\
**Post date:** [2018年五月6日 04:16 UTC](https://meta.discourse.org/t/webpush-gem-is-not-latest/86829/3 "2018-05-06T04:16:02Z")

</div>

I am packaging discourse as an rpm. And was wondering why we were using not the latest version for a feature that is just added. in general Gemfile dependencies tend to get stale especially when it is so tightly locked down as in this case.

---

<div class="post-metadata">

**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
**Post date:** [2018年五月6日 05:22 UTC](https://meta.discourse.org/t/webpush-gem-is-not-latest/86829/4 "2018-05-06T05:22:42Z")

</div>

> [@featheredtoast](#):
>
> What does that particular patch give you that you’re missing?

As best as I can determine the more recent version of the gem added JWT (JSON Web Token) headers. This could be important to authenticate the notification as coming from Discourse. But I am not knowledgeable enough in this area to know how applicable that is here.

---

<div class="post-metadata">

**Author:** ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)\
**Post date:** [2018年五月7日 16:54 UTC](https://meta.discourse.org/t/webpush-gem-is-not-latest/86829/5 "2018-05-07T16:54:08Z")

</div>

This is now no longer pinned per [Don't pin version for the webpush gem. · discourse/discourse@5993a3a · GitHub](https://github.com/discourse/discourse/commit/5993a3ae3a5dd279e8f823e58e09b7bd417f0615)

---

<div class="post-metadata">

**Author:** ![darix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darix/32/114280_2.png) [@darix](https://meta.discourse.org/u/darix)\
**Post date:** [2018年五月8日 11:24 UTC](https://meta.discourse.org/t/webpush-gem-is-not-latest/86829/6 "2018-05-08T11:24:27Z")

</div>

Thank you! This will make my life easier in the long run

---

<div class="post-metadata">

**Author:** ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)\
**Post date:** [2018年五月9日 01:00 UTC](https://meta.discourse.org/t/webpush-gem-is-not-latest/86829/7 "2018-05-09T01:00:06Z")

</div>

This topic was automatically closed after 32 hours. New replies are no longer allowed.