v6.2.1

Hotfix for missing --custom handlers and deprecation logic

v6.2.0

• deprecate --advanced flag, rename to --custom
• add checks for correct node version and kibana project checkout

v5.0.1

• bump @elastic/plugin-helpers to 5.0.1
  • Fixed the build task, thanks @meganwalker-ibm and @Kikketer!

v5.0.1-pre4

• Ask which Kibana version this plugin should track. Default option of master is preferred, but asking should make it clearer which version of Kibana this plugin supports

v5.0.1-pre3

• Generated plugins will always target "master" kibana
• bump plugin-helpers
  • ask for kibana version when building and plugin is tracking master
• git-ignore the build directory in generated plugins

v5.0.1-pre

• Bump plugin helpers version
• Fix npm run test:server and npm run test:browser tasks
• Add a stub test to the server
• Include chai assertion library by default

NOTE: Ideally releases of generator-kibana-plugin will be in sync with Kibana, so I've released this as v5.0.1-pre until Kibana 5.0.1 is released. Feedback welcome on this approach.

v5.0.0

• Ask about the target Kibana version and populate the version field in the package.json with that version
• Update the kibana-plugin-helpers

  • now npm run build properly builds plugins for Kibana 5.0+

  • additional args passed to npm run start will be passed to Kibana if they are passed after a --

     npm run start -- --host=0.0.0.0 --elasticsearch.url=https://XYZ.cloud.elastic.co