studio/meet
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

📝(doc) add an example for the frontend image

Browse Source 
I added an example in the documentation to ensure we remember to upgrade the
frontend image during the release process. This will help prevent any issues
related to outdated images when deploying new versions.

(I did this mistake while releasing)
This commit is contained in:
lebaudantoine
2024-08-05 23:11:18 +02:00
committed by aleb_the_flash
parent e7dc54d6c5
commit b783a8bac6
1 changed files with 19 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/release.md
View File

@@ -14,6 +14,14 @@ Whenever we are cooking a new release (e.g. `4.18.1`) we should follow a standar
repository: lasuite/meet-backend repository: lasuite/meet-backend
pullPolicy: Always pullPolicy: Always
tag: "v4.18.1" # Replace with your new version number, without forgetting the "v" prefix tag: "v4.18.1" # Replace with your new version number, without forgetting the "v" prefix
...
frontend:
image:
repository: lasuite/meet-frontend
pullPolicy: Always
tag: "v4.18.1" # Replace with your new version number, without forgetting the "v" prefix
``` ```
The new images don't exist _yet_: they will be created automatically later in the process. The new images don't exist _yet_: they will be created automatically later in the process.