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: CONTRIBUTING.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,11 +3,11 @@
3
3
4
4
## Releasing a new version
5
5
6
-
#### Making the package release
6
+
#### 1: Create release commit and tag
7
7
8
8
1. Make sure any changes made since last release in `main` are merged into `next`.
9
9
10
-
2. Checkout the `next` branch. Set the version number in the change log AND the `Version.cs` file.
10
+
2. Checkout the `next` branch. Set the version number in the change log AND the `BugsnagPerformance/Assets/BugsnagPerformance/Scripts/Internal/Version.cs` file.
11
11
12
12
3. Commit the changelog and version updates:
13
13
@@ -24,23 +24,22 @@
24
24
git push origin v1.x.x
25
25
```
26
26
27
-
6. Wait. The CI build will build the new package and create a draft release.
27
+
6. Create a release from the tag in github, copy the changelog entry into the release notes and publish the release.
28
28
29
-
7. Verify that the release looks good, upload the unity packages to the release, copy in the changelog entry into the release notes and publish the draft.
30
29
31
-
#### Making the UPM release
30
+
#### 2: Making the UPM release
32
31
33
-
Once the UnityPackage release is confirmed a UPM release should be deployed
32
+
Once the github release is confirmed a UPM release should be deployed
34
33
35
34
1. Checkout the release commit on `main`
36
35
37
36
2. Build the upm package by running the `build-upm-package.sh` script in the `upm` directory. You should pass the version number of the release like so `./build-upm-package.sh 1.x.x`. You must run the script from within the `upm` directory. This will build the upm package in the `upm/package` directory.
38
37
39
38
3. Test that the built package installs by using the install local package option in unity package manager.
40
39
41
-
4. Clone the `bugsnag-unity-performance-upm` repo and make sure you are in the `main` branch.
40
+
4. Clone the `bugsnag-unity-performance-upm` repo and make sure you are in the `main` branch and it is up to date with origin.
42
41
43
-
5. Replace the contents of the repo with the contents of the `upm/package` directory in the `bugsnag-unity-performance` repo
42
+
5. Replace the entire contents of the repo with the contents of the `upm/package` directory in the `bugsnag-unity-performance` repo
44
43
45
44
6. Commit these changes to main with the message `Release v1.x.x`
0 commit comments