grafana/packages
Torkel Ödegaard fe658d7ac2
Prometheus: Fixed Prometheus query editor error (plus new ErrorBoundaryAlert component) (#18838)
* ErrorHandling: Fixed Prometheus query editor error and added error boundary

* Update public/app/core/components/ErrorBoundary/ErrorBoundary.tsx

Co-Authored-By: kay delaney <45561153+kaydelaney@users.noreply.github.com>

* Fixed ts error
2019-09-02 20:45:18 +02:00
..
grafana-data DataFrame: split DataFrameHelper into MutableDataFrame and FieldCache (#18795) 2019-09-01 14:44:22 +02:00
grafana-runtime Add typings to package.json in packages (#18640) 2019-08-22 10:20:17 +02:00
grafana-toolkit Build: Optional skipping of typescript checking in dev bundler (#18772) 2019-08-30 14:02:31 +02:00
grafana-ui Prometheus: Fixed Prometheus query editor error (plus new ErrorBoundaryAlert component) (#18838) 2019-09-02 20:45:18 +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

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>