{"action":"closed","issue":{"url":"https://api.github.com/repos/elastic/kibana/issues/9179","repository_url":"https://api.github.com/repos/elastic/kibana","labels_url":"https://api.github.com/repos/elastic/kibana/issues/9179/labels{/name}","comments_url":"https://api.github.com/repos/elastic/kibana/issues/9179/comments","events_url":"https://api.github.com/repos/elastic/kibana/issues/9179/events","html_url":"https://github.com/elastic/kibana/issues/9179","id":191023459,"number":9179,"title":"Prevent plugins from breaking after minor Kibana updates","user":{"login":"Dom-nik","id":3912570,"avatar_url":"https://avatars.githubusercontent.com/u/3912570?v=3","gravatar_id":"","url":"https://api.github.com/users/Dom-nik","html_url":"https://github.com/Dom-nik","followers_url":"https://api.github.com/users/Dom-nik/followers","following_url":"https://api.github.com/users/Dom-nik/following{/other_user}","gists_url":"https://api.github.com/users/Dom-nik/gists{/gist_id}","starred_url":"https://api.github.com/users/Dom-nik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Dom-nik/subscriptions","organizations_url":"https://api.github.com/users/Dom-nik/orgs","repos_url":"https://api.github.com/users/Dom-nik/repos","events_url":"https://api.github.com/users/Dom-nik/events{/privacy}","received_events_url":"https://api.github.com/users/Dom-nik/received_events","type":"User","site_admin":false},"labels":[{"id":470241278,"url":"https://api.github.com/repos/elastic/kibana/labels/:Platform","name":":Platform","color":"fef2c0","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-11-22T14:35:04Z","updated_at":"2016-11-22T14:58:54Z","closed_at":"2016-11-22T14:58:54Z","body":"**Kibana version**: 5.0.x\r\n\r\n**Describe the feature**:\r\nThe problem I'm describing is rather predictable/obvious, but quite frustrating.\r\nThe 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. \r\nPlease implement different version checking, so that minor updates don't break plugins.\r\n\r\n**Extra:**\r\nThere are two workarounds I found, but they are manual and shouldn't be end users' problem. It seems that the second one can be a permanent solution, if it gets adopted by plugin developers:\r\n\r\n1. Do as follows:\r\na) download your plugin, \r\nb) unzip it into $KIBANA_HOME/plugins,\r\nc) change \"version\" in the package.json file to match your Kibana version, e.g.: \"version\": \"5.0.1\"\r\nThis requires changing after each update.\r\n\r\n2. 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 - it seems that whis will work for all further updates, but is less safe.\r\n\r\nPlease refer to: https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401"}}
{"actor":{"display_login":"epixa"}}