From 245be481fdd8856a39391ddfb76b30814285b330 Mon Sep 17 00:00:00 2001 From: Jack Westbrook Date: Mon, 3 Mar 2025 12:00:45 +0100 Subject: [PATCH] docs(packages): update readme fixed version nx group name --- packages/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/README.md b/packages/README.md index 9334a990b96..c686940fa60 100644 --- a/packages/README.md +++ b/packages/README.md @@ -6,7 +6,7 @@ This document contains information about Grafana frontend package versioning and We use [Nx](https://nx.dev/recipes/nx-release/get-started-with-nx-release) for package versioning. -All packages defined within the [nx.json `fixed` release group](../nx.json) are versioned according to the current Grafana version: +All packages defined within the [nx.json `grafanaPackages` release group](../nx.json) 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 @@ -26,7 +26,7 @@ Alpha and beta releases are published under the `next` tag on npm. ### Automatic prereleases -Every commit to main that has changes within the `packages` directory is a subject of npm packages release. _ALL_ packages must be released under version from package.json file with the drone build number added to it: +Every commit to main that has changes within the `packages` directory is subject to an npm release. _ALL_ packages must be released under version from package.json file with the drone build number added to it: ``` -