# Plugins break after upgrade 5.0.0 -\> 5.0.1 **URL:** \ **Category:** Kibana\ **Created:** [November 17, 2016, 1:55pm UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401 "2016-11-17T13:55:04Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Dom-nik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dom-nik/32/13243_2.png) [@Dom-nik](https://discuss.elastic.co/u/Dom-nik)\ **Post date:** [November 17, 2016, 1:55pm UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401/1 "2016-11-17T13:55:04Z")
Hello, The problem I'm describing is rather predictable/obvious, but quite frustrating. The release cycle for Kibana is very fast and the plugins that worked fine for Kibana 5.0.0 break (to be precise: get turned off because of version discrepancy) after an upgrade to 5.0.1, even though it seems that such small upgrade (bugfixes mostly) shouldn't break them. Is there any way to prevent this except for waiting for plugin updates or sticking with an older version of Kibana? Maybe it would make sense to allow using 5.0.0 plugins with all 5.0.x versions and let the user decide if they work as expected? I'm referring to [these plugins](https://github.com/elastic/kibana/wiki/Known-Plugins). ---
**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\ **Post date:** [November 17, 2016, 2:26pm UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401/2 "2016-11-17T14:26:05Z")
+1 I would even go as far to say, 5.x.x there should be no breaking changes between minor releases either. Or how about the way node does it say "\>5.0.1" so the plugin says it needs "Greater then Version 5.0.0 ---
**Author:** ![Dom-nik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dom-nik/32/13243_2.png) [@Dom-nik](https://discuss.elastic.co/u/Dom-nik)\ **Post date:** [November 17, 2016, 5:36pm UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401/3 "2016-11-17T17:36:59Z")
Is the discuss forum the right place for such talk or should we maybe move to GitHub Issues? ---
**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\ **Post date:** [November 18, 2016, 4:21am UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401/4 "2016-11-18T04:21:02Z")
well probably both, a discussion is always right on a forum, an issue should also be opened for action. 😃 ---
**Author:** ![Dom-nik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dom-nik/32/13243_2.png) [@Dom-nik](https://discuss.elastic.co/u/Dom-nik)\ **Post date:** [November 18, 2016, 1:14pm UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401/5 "2016-11-18T13:14:13Z")
There are two workarounds I found: 1. Do as follows: a) download your plugin, b) unzip it into $KIBANA\_HOME/plugins, c) change "version" in the package.json file to match your Kibana version, e.g.: "version": "5.0.1" This requires changing after each update. 2. Do as in 1, but change "version" to "kibana" ("version": "kibana"), the same way it is set up in core plugins ($KIBANA\_HOME/src/core\_plugins), as proposed by one of the plugin developers: [https://github.com/JuanCarniglia/area3d\_vis/issues/1](https://github.com/JuanCarniglia/area3d_vis/issues/1) - it seems that whis will work for all further updates, but is less safe. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 21, 2016, 2:55am UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401/6 "2016-11-21T02:55:00Z")
Please do raise this on Github as well 🙂 ---
**Author:** ![Dom-nik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dom-nik/32/13243_2.png) [@Dom-nik](https://discuss.elastic.co/u/Dom-nik)\ **Post date:** [November 22, 2016, 3:24pm UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401/7 "2016-11-22T15:24:15Z")
I did ([#9179](https://github.com/elastic/kibana/issues/9179)), but it got closed almost immediately. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 22, 2016, 10:00pm UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401/8 "2016-11-22T22:00:02Z")
As a duplicate, did you se the linked issue - [https://github.com/elastic/kibana/issues/9019](https://github.com/elastic/kibana/issues/9019) ---
**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\ **Post date:** [November 28, 2016, 10:21pm UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401/9 "2016-11-28T22:21:15Z")
Yah I was reading that chain of conversation. I don't like the tone of it, basically from reading the conversation Elastic developers are saying tough we want tight validation of the plugins so they don't have to have to worry about backwards compatibility. I am sorry but at the pace Elastic is moving you have to start guaranteeing some kind of compatibility between point releases. You can't keep making breaking changes all the time. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 26, 2016, 10:21pm UTC](https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401/10 "2016-12-26T22:21:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.