mirror of https://github.com/grafana/grafana.git synced 2026-08-19 01:34:54 -05:00

Files

T

Dominik Prokop c9b11bfc7a ReactMigration: Migrate DataSource HTTP Settings to React (#19452 )

* Basic components for HTTP settings migration WIP

* Add secureJsonFields to DataSourceSettings

* Introduce datasource-http-settings-next directive for backward compatibility

* fix lint

* renames

* rename fix

* TagsInput component

* move tags from app to grafana/ui

* implement tagsinput on datasourcesettings

* capitalize

* new file for react directive for testing

* some layout touch ups

* FormField story

* Minor touch ups

* add url validation

* using prevent default to prevent updating datasource when adding tag

* using Stylefactory and fix tslint issue on MouseEvent

* only show tlsauthsettings if tls or ca cert

* fix url input length

* fix for showAccessOptions

* Implemented CertTextArea, removed commented code

* removed commented / not used code

* Rename and add more elements to Certification component

* fixing newSecureJsonData

* spelling

* Fix issue with checkboxes being undefined

* Removed old partials and minor fix

* removed unused props from story

2019-10-18 12:09:53 +02:00

grafana-data

DataFrame: guess number field when on NaN (#19833 )

2019-10-16 15:13:27 +02:00

grafana-runtime

Chore: Bump typescript to version 3.6.3 (#19308 )

2019-09-24 10:40:16 +01:00

grafana-toolkit

@grafana/toolkit: Check if git user.name config is set (#19821 )

2019-10-16 08:04:24 +02:00

grafana-ui

ReactMigration: Migrate DataSource HTTP Settings to React (#19452 )

2019-10-18 12:09:53 +02:00

README.md

Update README.md (#19457 )

2019-10-12 12:53:47 +02:00

tsconfig.json

Packages: create shared tsconfig.json (#18010 )

2019-07-10 12:50:52 +02:00

README.md

Grafana frontend packages

This document contains information about Grafana frontend package versioning and releases.

Versioning

We use Lerna for packages versioning and releases.

All packages are versioned according to the current Grafana version:

Grafana v6.3.0-alpha1 -> @grafana/* packages @ 6.3.0-alpha.1
Grafana v6.2.5 -> @grafana/* packages @ 6.2.5
Grafana - master branch version (based on package.json, i.e. 6.4.0-pre) -> @grafana/* packages @ 6.4.0-pre- (see details below about packages publishing channels)

Please note that @grafana/toolkit, @grafana/ui, @grafana/data, and @grafana/runtime packages are considered ALPHA even though they are not released as alpha versions.

Stable releases

Even though packages are released under a stable version, they are considered ALPHA until further notice!

Stable releases are published under the latest tag on npm.

Alpha and beta releases

Alpha and beta releases are published under the next tag on npm.

Automatic prereleases

Every commit to master that has changes within the packages directory is a subject of npm packages release. ALL packages must be released under version from lerna.json file with commit SHA added to it:

<lerna.json version>-<COMMIT_SHA>

Automatic prereleases are published under the canary dist tag.

Manual release

All of the steps below must be performed on a release branch, according to Grafana Release Guide.

Make sure you are logged in to npm in your terminal and that you are a part of Grafana org on npm.

Run yarn packages:prepare script from the root directory. This performs tests on the packages and prompts for the version of the packages. The version should be the same as the one being released.
- Make sure you use semver convention. So, place a dot between prerelease id and prerelease number, i.e. 6.3.0-alpha.1
- Make sure you confirm the version bump when prompted!
Commit changes (lerna.json and package.json files) - "Packages version update: <VERSION>"
Run yarn packages:build script that prepares distribution packages in packages/grafana-*/dist. These directories are going to be published to npm.
Depending whether or not it's a prerelease:
- When releasing a prerelease run packages:publishNext to publish new versions.
- When releasing a stable version run packages:publishLatest to publish new versions.
Push version commit to the release branch.

Building individual packages

To build individual packages, run:

grafana-toolkit package:build --scope=<ui|toolkit|runtime|data>