IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-02-20 11:48:34 -06:00
Code Issues Packages Projects Releases Wiki Activity
3c61b563c3
grafana/packages
History
Peter Holmberg 3c61b563c3 Ldap: Add LDAP debug page (#18759) 
* Add items for navmodel and basic page

* add reducer and actions

* adding user mapping table component

* adding components for ldap tables

* add alert box on error

* close error alert box

* LDAP status page: connect APIs WIP

* LDAP debug: fetch connection status from API

* LDAP debug: fetch user info from API

* LDAP debug: improve connection error view

* LDAP debug: connection error tweaks

* LDAP debug: fix role mapping view

* LDAP debug: role mapping view tweaks

* LDAP debug: add bulk-sync button stub

* LDAP debug: minor refactor

* LDAP debug: show user teams

* LDAP debug: user info refactor

* LDAP debug: initial user page

* LDAP debug: minor refactor, remove unused angular wrapper

* LDAP debug: add sessions to user page

* LDAP debug: tweak user page

* LDAP debug: tweak view for disabled user

* LDAP debug: get sync info from API

* LDAP debug: user sync info

* LDAP debug: sync user button

* LDAP debug: clear error on page load

* LDAP debug: add user last sync info

* LDAP debug: actions refactor

* LDAP debug: roles and teams style tweaks

* Pass showAttributeMapping to LdapUserTeams

* LDAP debug: hide bulk sync button

* LDAP debug: refactor sessions component

* LDAP debug: fix loading user sessions

* LDAP debug: hide sync user button

* LDAP debug: fix fetching unavailable /ldap-sync-status endpoint

* LDAP debug: revert accidentally added fix

* LDAP debug: show error when LDAP is not enabled

* LDAP debug: refactor, move ldap components into ldap/ folder

* LDAP debug: styles refactoring

* LDAP debug: ldap reducer tests

* LDAP debug: ldap user reducer tests

* LDAP debug: fix connection error placement

* Text update

* LdapUser: Minor UI changes moving things around

* AlertBox: Removed icon-on-top as everywhere else it is centered, want to have it be consistent
2019-09-16 18:56:01 +03:00
..
grafana-data Chore: cross-package security bumps (#19131) 2019-09-16 15:50:15 +02:00
grafana-runtime Ldap: Add LDAP debug page (#18759) 2019-09-16 18:56:01 +03:00
grafana-toolkit Chore: cross-package security bumps (#19131) 2019-09-16 15:50:15 +02:00
grafana-ui Chore: cross-package security bumps (#19131) 2019-09-16 15:50:15 +02:00
README.md Packages: update versioning and release process (#18195) 2019-09-12 08:00:31 +02:00
tsconfig.json Packages: create shared tsconfig.json (#18010) 2019-07-10 12:50:52 +02:00

README.md

Grafana frontend packages

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 & @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 latest tag on npm.

Alpha and beta releases

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

Automatic pre-releases

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

<lerna.json version>-<COMMIT_SHA>

Automatic prereleases are published under canary dist tag.

Manual release

All of the steps below should 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

  1. Run yarn packages:prepare script from root directory. This will perform tests on the packages and prompt for 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 prelease number!!! i.e. 6.3.0-alpha.1
  • Make sure you confirm the version bump when prompted!
  1. Commit changes (lerna.json & package.json files) - "Packages version update: <VERSION>"
  2. Run yarn packages:build script that will prepare distribution packages in packages/grafana-*/dist. These directories are going to be published to npm
  3. Depending whether or not it's a prerelease:
  • When releasing a prelease run packages:publishNext to publish new versions.
  • When releasing a stable version run packages:publishLatest to publish new versions.
  1. Push version commit to the release branch

Building individual packages

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