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: .github/WORKFLOWS.md
+27-13Lines changed: 27 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,13 +54,13 @@ Once changes are merged into the `main` branch, workflows prepare the project fo
54
54
Detects documentation updates and publishes the latest content to the documentation site.
55
55
56
56
## Release Time
57
-
Paladin follows a two-stage release process to ensure quality and stability:
57
+
Paladin follows a two-stage release process to ensure quality and stability. All releases are triggered through the **[Release Entry Point](https://github.com/LFDT-Paladin/paladin/actions/workflows/release-entry.yaml)** workflow due to the way npm trusted publishing works.
Builds and **publishes Docker images** tagged with the release version (e.g., `v1.2.3`) and `latest`.
85
85
-**Registries:**
@@ -101,29 +101,45 @@ Once the RC has been tested and validated, the final release can be created:
101
101
102
102
## How to Create a Release
103
103
104
+
All releases are triggered through the unified **[Release Entry Point](https://github.com/LFDT-Paladin/paladin/actions/workflows/release-entry.yaml)** workflow.
105
+
104
106
### Quick Start: Release Process
105
107
Follow these steps to create a new Paladin release:
106
108
107
109
#### Step 1: Create a Release Candidate
108
-
1. Go to **[Actions → Release Candidate](https://github.com/LFDT-Paladin/paladin/actions/workflows/release-candidate.yaml)**
110
+
1. Go to **[Actions → Release Entry Point](https://github.com/LFDT-Paladin/paladin/actions/workflows/release-entry.yaml)**
109
111
2. Click **"Run workflow"**
110
-
3. Enter the RC tag (e.g., `v1.2.3-rc.1`)
112
+
3. Fill in the required fields:
113
+
-**release_type**: Select `rc`
114
+
-**tag**: RC tag (e.g., `v1.2.3-rc.1`)
111
115
4. Click **"Run workflow"**
112
116
5. Wait for the workflow to complete and test the RC thoroughly
113
117
114
118
#### Step 2: Create the Final Release
115
-
1. Go to **[Actions → Release](https://github.com/LFDT-Paladin/paladin/actions/workflows/release.yaml)**
119
+
1. Go to **[Actions → Release Entry Point](https://github.com/LFDT-Paladin/paladin/actions/workflows/release-entry.yaml)**
116
120
2. Click **"Run workflow"**
117
121
3. Fill in the required fields:
122
+
-**release_type**: Select `final`
118
123
-**tag**: Final release version (e.g., `v1.2.3`)
119
124
-**rc_tag**: The RC tag you tested (e.g., `v1.2.3-rc.1`)
120
125
-**latest**: Check if this should be marked as the latest release
121
126
4. Click **"Run workflow"**
122
127
128
+
#### SDK-Only Release (Optional)
129
+
To release only the TypeScript SDK without a full release:
130
+
1. Go to **[Actions → Release Entry Point](https://github.com/LFDT-Paladin/paladin/actions/workflows/release-entry.yaml)**
131
+
2. Click **"Run workflow"**
132
+
3. Fill in the required fields:
133
+
-**release_type**: Select `sdk`
134
+
-**tag**: SDK version (e.g., `v1.2.3`)
135
+
-**sdk_dist_tags**: NPM dist-tags, semicolon-separated (e.g., `latest` or `rc;rc.1`)
136
+
-**ref**: (Optional) Commit ref for checkout, defaults to workflow branch
137
+
4. Click **"Run workflow"**
138
+
123
139
### Example Release Flow
124
140
```
125
-
1. Create RC: v1.2.3-rc.1 → Test thoroughly
126
-
2. Final Release: v1.2.3 → Built from v1.2.3-rc.1
141
+
1. Create RC: release_type=rc, tag=v1.2.3-rc.1 → Test thoroughly
142
+
2. Final Release: release_type=final, tag=v1.2.3, rc_tag=v1.2.3-rc.1
127
143
```
128
144
129
145
### Important Release Process Notes:
@@ -239,12 +255,10 @@ You will publish a Helm chart version `0.11.0-fix.0` that points to images built
239
255
## Manual Actions 🛠️
240
256
Workflows can also be triggered manually when needed. Available options include:
241
257
258
+
-**[Release Entry Point](workflows/release-entry.yaml)** (RC, final, and SDK releases)
0 commit comments