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: RELEASE.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,21 +10,22 @@ You can manually trigger the release workflow from the [GitHub Actions UI](https
10
10
11
11
### **Before triggering a release**
12
12
13
-
1. Create a release branch and update the **`version`** field in `packages/<package_name>/package.json` to the intended release version.
13
+
1. Create a release branch. A qualified branch name should start with "release-" or "release/", case-insensitive. e.g: `release/xrpl@4.3.8`, `release-xrpl-4.3.8`, `Release/xrpl@4.3.8`.
14
+
2. Update the **`version`** field in `packages/<package_name>/package.json` to the intended release version.
14
15
```json
15
16
{
16
17
"name": "<package_name>",
17
18
"version": "x.y.z"
18
19
}
19
20
```
20
-
2. Run npm i to update the package-lock with the updated versions and commit the lock file to the releaes branch
21
+
3. Run npm i to update the package-lock with the updated versions and commit the lock file to the release branch
21
22
22
23
### **Triggering a Release**
23
24
24
25
1. Go to **GitHub → Actions → Release Pipeline → Run workflow**
25
-
2. Fill in these fields:
26
+
2. Choose the release branch from dropdown
27
+
3. Fill in these fields:
26
28
-**package_name** → The folder name under `packages/`, e.g., `xrpl` or `ripple-address-codec`.
27
-
-**release_branch** → The Git branch the release is generated from, e.g., `release/xrpl@4.3.8`.
28
29
-**npmjs_dist_tag** → The npm distribution tag to publish under. Defaults to `latest`.
29
30
- Examples:
30
31
-`latest` → Standard production release
@@ -36,13 +37,12 @@ You can manually trigger the release workflow from the [GitHub Actions UI](https
36
37
| Field | Example |
37
38
|------------------|-----------------------|
38
39
| package_name | xrpl |
39
-
| release_branch | release/xrpl@4.3.8 |
40
40
| npmjs_dist_tag | latest |
41
41
42
42
43
43
### **Reviewing the release details and scan result**
44
44
45
-
1. The pipeline will pause at the "Review test and security scan result" step, at least 2 approvers are required to review and approve the release.
45
+
1. The pipeline will pause at the "Print Test/Security scan result and invite Dev team to review" step and also before the final release step, relevant team should review the release details and scan result.
0 commit comments