From 74e120a43acfc2e4dab2ec27901f41bedf6cd4f6 Mon Sep 17 00:00:00 2001 From: Naveen MR Date: Mon, 4 Jul 2022 00:04:03 +0100 Subject: [PATCH] docs : Builds & releases --- .../noco-docs/content/en/engineering/builds-and-releases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/noco-docs/content/en/engineering/builds-and-releases.md b/packages/noco-docs/content/en/engineering/builds-and-releases.md index dd5c537d34..77d19c095d 100644 --- a/packages/noco-docs/content/en/engineering/builds-and-releases.md +++ b/packages/noco-docs/content/en/engineering/builds-and-releases.md @@ -36,7 +36,7 @@ Why? Sometimes we may mess up in NPM deployment. As NPM doesn't allow us to rede - Once `release-docker` is finished, then test it locally first. You'll be expected to see `Upgrade Available` notification in UI as we haven't published the release note. (the version is retrieved from there) - Once everything is finished, then publish the release note and the deployment is considered as DONE. -## Jobs Explanations +## Release action explained ### validate-branch