IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-02-25 18:55:37 -06:00
Code Issues Packages Projects Releases Wiki Activity
Files
de705229ba3257e04d9590750e80fd50a6664192
grafana/packages
History
Dominik Prokop de705229ba Build: Release packages under next tag when changes detected on master (#18062) 
* Testing lerna on circle

* Remove dependency on test task, fix yarn

* yarn fix

* Run lerna from local bin

* Use packages cache, run lern via npx

* Add packages:build

* Install packages before release

* Remove cache tmp

* add lerna bootstrap

* temporarily add tsignore

* lerna add data package to ui

* Remove @types/lodas resolution

* Try any...

* Typo fix

* Add publishing packages

* update lerna publish script

* Reset git befgore publishing package

* Correct lerna version

* Packages version bump

* Remove postpublish

* Publish to npm

* Set git creds before commit

* Rename job and run it after frontend tests and build passes

* Run next packages release on master but not when tagged with release

* Minor copy

* Update circle's config

* Fix config
2019-07-15 14:19:08 +02:00
..
grafana-data
Build: Release packages under next tag when changes detected on master (#18062)
2019-07-15 14:19:08 +02:00
grafana-runtime
Build: Release packages under next tag when changes detected on master (#18062)
2019-07-15 14:19:08 +02:00
grafana-toolkit
Build: Release packages under next tag when changes detected on master (#18062)
2019-07-15 14:19:08 +02:00
grafana-ui
Build: Release packages under next tag when changes detected on master (#18062)
2019-07-15 14:19:08 +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>