chore: complete release docs with release-please

Author: aldbr

docs/dev/how-to/make-a-release.md docs/admin/how-to/make-a-release.mddocs/dev/how-to/make-a-release.md renamed to docs/admin/how-to/make-a-release.md

@@ -25,6 +25,31 @@ Execute the following points in the presented order.
 
 At this stage, there is a new `diracx` and `diracx-chart` release.
 
+# How to make a new DiracX-Web release
+
+Execute the following points in the presented order.
+
+1. Find the `release-please` [pull request](https://github.com/DIRACGrid/diracx-web/pulls?q=is%3Apr+is%3Aopen+%22chore%28main%29%3A+release%22) for your release. If you can't find it, it means that the currently existing latest release includes already all code changes.
+
+2. Review the release number **and** the content of the changelog
+
+    - If you need to change the release number, follow the [`release-please` doc](https://github.com/googleapis/release-please?tab=readme-ov-file#how-do-i-change-the-version-number)
+
+    ```bash
+    git commit --allow-empty -m "chore: release 0.0.3" -m "Release-As: v0.0.3"
+    git push upstream HEAD:main
+    ```
+
+    - If you want to update the release notes manually, follow the [`release-please` doc](https://github.com/googleapis/release-please?tab=readme-ov-file#how-can-i-fix-release-notes)
+
+3. Merge the `release-please` PR
+
+4. Check the [deployment action](https://github.com/DIRACGrid/diracx-web/actions/workflows/deployment.yml?query=event%3Apush)
+
+5. When the above is finished, check that the [CI](https://github.com/DIRACGrid/diracx-charts/actions/workflows/chart-ci.yml) in `diracx-charts` is successful
+
+At this stage, there is a new `diracx-web` release and `diracx-chart` release.
+
 ## Making the extension release
 
 Making a release of an extension depends on how the extension has been set up. Below are recommended workflows:

docs/dev/reference/making-releases.md docs/admin/reference/making-releases.mddocs/dev/reference/making-releases.md renamed to docs/admin/reference/making-releases.md

@@ -52,7 +52,11 @@ flowchart LR
 
 ## diracx release
 
-Releases are managed by `ReleasePlease`. The token used to perform it belongs to `diracbot` github user
+Releases are managed by `ReleasePlease`. The token used to perform it belongs to `DIRACGridBot` github user.
+
+!!! info "Why a bot token?"
+
+    `GITHUB_TOKEN` cannot trigger downstream workflows (GitHub's anti-loop protection). Using a bot PAT ensures that the tag created by `release-please` triggers the deployment and chart update jobs.
 
 A new release creates:
 
@@ -69,6 +73,21 @@ git commit --allow-empty -m "chore: release 0.0.3" -m "Release-As: v0.0.3"
 git push upstream HEAD:main
 ```
 
+## diracx-web release
+
+Releases are managed by `ReleasePlease`. The token used to perform it belongs to `DIRACGridBot` github user, same as `diracx`.
+
+!!! info "Why a bot token?"
+
+    `GITHUB_TOKEN` cannot trigger downstream workflows (GitHub's anti-loop protection). Using a bot PAT ensures that the tag created by `release-please` triggers the deployment and chart update jobs.
+
+A new release creates:
+
+- a [github release](https://github.com/DIRACGrid/diracx-web/releases)
+- an [npm release](https://www.npmjs.com/package/@dirac-grid/diracx-web-components) for `diracx-web-components`
+- new [docker images](https://github.com/DIRACGrid/diracx-web/)
+- updated [Storybook documentation](https://diracgrid.github.io/diracx-web/) on GitHub Pages
+
 ## diracx-charts releases
 
 Every commit in master triggers a new release. The releases are published on a [helm repo](https://charts.diracgrid.org/index.yaml)

mkdocs.yml

@@ -92,7 +92,7 @@ nav:
       - Debugging: admin/how-to/debugging.md
       - Upgrading: admin/how-to/upgrading.md
       - Rotate a secret: admin/how-to/rotate-a-secret.md
-      - Make a release: dev/how-to/make-a-release.md
+      - Make a release: admin/how-to/make-a-release.md
     - Explanations:
       - admin/explanations/index.md
       - Auth in DiracX: admin/explanations/auth-with-diracx.md
@@ -112,7 +112,7 @@ nav:
       - Security Model: admin/reference/security_model.md
       - Settings and Preferences: admin/reference/settings-and-preferences.md
       - Environment variables: admin/reference/env-variables.md
-      - Making and deploying releases: dev/reference/making-releases.md
+      - Making and deploying releases: admin/reference/making-releases.md
       - Charts values: admin/reference/values.md
       - RUN_PROD.md
       - SSO.md