# Associating plugin versions with Discourse versions

**URL:** <https://meta.discourse.org/t/associating-plugin-versions-with-discourse-versions/59841>\
**Category:** Development\
**Created:** [3월 24, 2017, 1:34오후 UTC](https://meta.discourse.org/t/associating-plugin-versions-with-discourse-versions/59841 "2017-03-24T13:34:00Z")\
**Posts on this page:** 1\
**Showing post:** 1

<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:** [3월 24, 2017, 1:34오후 UTC](https://meta.discourse.org/t/associating-plugin-versions-with-discourse-versions/59841/1 "2017-03-24T13:34:01Z")

</div>

Continuing the discussion from [Babble - A Chat Plugin](https://meta.discourse.org/t/babble-a-chat-plugin/31753/626):

I have noticed this problem come up a few times here.  
Often the solution is “update your version of Discourse, update your version of the plugin”

This works fine as long as one is able and willing to update, But there are times when that is not an option, eg. when the version of Discourse is Stable.

I have always worked on localhost with the current latest version so I might have missed something, but I’m wondering if there is an easy way to “tie” a plugin version to a particular Discourse version.  
Perhaps the plugin API number can already do this?  
If not, maybe a type of “#compatibility” or “#requires” comment could be added to the plugin.rb file that if not used by code could at least be found when problems arise because of version conflicts?

---

_[View the full topic](https://meta.discourse.org/t/associating-plugin-versions-with-discourse-versions/59841)._