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
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,32 @@ There are a few steps to getting started:
28
28
4. Add the user to the `isomerpages` organisation by adding them to the file [here](https://github.com/opengovsg/isomer-infra/blob/main/src/github/constants.ts)
29
29
5. Add the user to the relevant github teams [here](https://github.com/orgs/opengovsg/teams?query=isomer) by asking the maintainer
30
30
31
+
### Cutting a release
32
+
33
+
We run releases via the `publish` event. Hence, in order to cut a release, we have to go through the following steps:
34
+
35
+
1. first, select the release commit
36
+
2. generate a tag for the release commit from the previous tag as follows:
37
+
- if you're making a hotfix, add a 0.0.1 to the previous version
38
+
- if you're making a minor upgrade, add a 0.1 to the previous version.
39
+
- for all purposes, all our releases are minor upgrades so we will not be incrementing the major version number
40
+
3. push the tag to the remote origin
41
+
4. go to github and click on `Tags`
42
+
5. next, click on releases and draft a new release
43
+
6. choose the tag you have previously created
44
+
7. generate release notes (this can be done automatically via the button)
45
+
8. publish the release
46
+
47
+
### Running database migrations
48
+
49
+
1. first, add the relevant `.pem` file to the `apps/studio/ssh` folder
50
+
- this can be found by searching for `AWS Isomer Next <env> Bastion SSH Key` in your 1Password vault
51
+
2. Next, duplicate the `.env.example` in `apps/studio` to `.ssh/.env.<env>`
52
+
3. Fill in the relevant information by searching for `Isomer Next <env> Database` inside 1password
53
+
4. Next, run `npm run jump:<env>` from within the `apps/studio` folder
54
+
5. Next, run `npm run migrate:<env>` from within the `apps/studio` folder
55
+
6. (Optional) If you need to run a seed, run `npm run db:seed`
0 commit comments