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: docs/RELEASE.md
+19-7
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,21 @@ This is normally performed by our CI system. However, there are important steps
10
10
11
11
In order to cut a release, you must:
12
12
13
-
1. If this is a new major or minor version - but **not** just a patch change - update [metadata.yaml](../metadata.yaml) to add it, and map it to the correct cluster-api contract version
14
-
1. Update [packet-ci-actions.yaml](../test/e2e/config/packet-ci-actions.yaml) and [packet-ci.yaml](../test/e2e/config/packet-ci.yaml) to use the new version number for the current and/or new contract version of the packet InfrastructureProvider.
15
-
1. If this is a new major or minor version - but **not** just a patch chagne - update [packet-ci-actions.yaml](../test/e2e/config/packet-ci-actions.yaml) and [packet-ci.yaml](../test/e2e/config/packet-ci.yaml) to have a new "next" version number for the latest contract version of the packet InfrastructureProvider.
13
+
1. Update [packet-ci-actions.yaml](../test/e2e/config/packet-ci-actions.yaml) and [packet-ci.yaml](../test/e2e/config/packet-ci.yaml) to use the new version number for the current and/or new contract version of the packet InfrastructureProvider. (ie. v0.9.1)
14
+
1. If this is a new major or minor version - but **not** just a patch change:
15
+
16
+
- Update [metadata.yaml](../metadata.yaml) to add it, and map it to the correct cluster-api contract version
17
+
18
+
```yaml
19
+
- major: 0
20
+
minor: 10
21
+
contract: v1beta1
22
+
```
23
+
24
+
- Update [packet-ci-actions.yaml](../test/e2e/config/packet-ci-actions.yaml) and [packet-ci.yaml](../test/e2e/config/packet-ci.yaml) to have a new "next" version number for the latest contract version of the packet InfrastructureProvider (ie. v0.11.99).
25
+
- Update clusterctl-settings.json to have the new "next" version number for the latest contract version of the packet InfrastructureProvider (ie. v0.11.99).
26
+
27
+
1. Review and update the versions of installed deployments like CPEM and kube-vip inside the templates.
16
28
1. Commit the changes.
17
29
1. Push out your branch, open a PR and merge the changes
18
30
1. Wait for the Continuous Integration github action to finish running
@@ -21,7 +33,7 @@ In order to cut a release, you must:
21
33
22
34
## How A Release Happens
23
35
24
-
* GitHub Actions detects a new tag has been pushed
25
-
* CI builds docker images for each supported architecture as well as a multi-arch manifest, and tags it with the semver tag of the release, e.g. `v0.4.0`
26
-
* CI creates the release in `out/release`, the equivalent of `make release`
27
-
* CI copies the artifacts in `out/release/*` to the github releases
36
+
-GitHub Actions detects a new tag has been pushed
37
+
-CI builds docker images for each supported architecture as well as a multi-arch manifest, and tags it with the semver tag of the release, e.g. `v0.4.0`
38
+
-CI creates the release in `out/release`, the equivalent of `make release`
39
+
-CI copies the artifacts in `out/release/*` to the github releases
0 commit comments