You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-5Lines changed: 21 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,11 +39,27 @@ gh run watch
39
39
```
40
40
41
41
**How it works:**
42
-
1. Workflow fetches the correct commit SHA from wire-server releases
43
-
2. Updates all charts that match the current wire-server version to the pinned version
44
-
3. Updates both version numbers and commit metadata
45
-
4. Creates a new commit and pushes to the branch
46
-
5. Triggers PR creation to wire-server-deploy
42
+
1. Workflow creates a temporary branch from the base branch (e.g., `offline`)
43
+
2. Fetches the correct commit SHA from wire-server releases
44
+
3. Updates all charts that match the current wire-server version to the pinned version
45
+
4. Modifies root `build.json` with pinned versions
46
+
5. Commits the changes and creates a Git tag: `pinned-<branch>-<version>`
47
+
6. Pushes the tag to remote and deletes the temporary branch
48
+
7. Creates a PR to wire-server-deploy using the tag name
49
+
50
+
**Important:** The root `build.json` on the base branch (e.g., `offline`) remains unchanged at the latest version. Pinned versions are accessible via Git tags (e.g., `pinned-offline-5.23.0`) and referenced by clean URLs.
51
+
52
+
**Example after pinning to 5.23.0:**
53
+
```
54
+
offline branch: build.json at 5.24.0 (unchanged)
55
+
Git tag: pinned-offline-5.23.0 → points to commit with build.json at 5.23.0
0 commit comments