IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-02-13 09:05:45 -06:00
Code Issues Packages Projects Releases Wiki Activity
f22aaa5518
grafana/packages
History
Shavonn Brown f22aaa5518 Azure Monitor and Log Analytics converted and separated into components (#18259) 
* Azure Monitor and Log Analytics converted and separated into components

* Insights creds converted

* remove angular config

* fix workspaces and missing sameas key

* fix workspace save

* set subscriptionId key

* editor fields, load workspaces btn

* workspace load req fields updated

* added tooltip to switch, disable buttons instead of hide

* master merge and tests
2019-08-19 23:35:44 +02:00
..
grafana-data Refactor: move KeyValue and deprecation warning to @grafana/data (#18582) 2019-08-16 11:10:32 +02:00
grafana-runtime grafana/toolkit: improve CI task (#18189) 2019-08-03 12:34:02 -07:00
grafana-toolkit Toolkit: write PR report to a folder with the circle build number (#18560) 2019-08-14 14:06:43 -07:00
grafana-ui Azure Monitor and Log Analytics converted and separated into components (#18259) 2019-08-19 23:35:44 +02:00
README.md Packages: Use lerna for release orchestration (#17985) 2019-07-09 09:43:53 -07:00
tsconfig.json Packages: create shared tsconfig.json (#18010) 2019-07-10 12:50:52 +02:00

README.md

Grafana frontend packages

Releasing new version

We use Lerna for packages versioning and releases

Manual release

  1. Run packages:prepare script from root directory. This will perform cleanup, run all tests and bump version for all packages. Also, it will create @packages@[version] tag and version bump commit with Packages: publish [version] message.
  2. Run packages:build script that will prepare distribution packages.
  3. Run packages:publish to publish new versions
    • add --dist-tag next to publish under next tag
  4. Push version commit

Building individual packages

To build induvidual packages run grafana-toolkit package:build --scope=<ui|toolkit|runtime|data>