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: RELEASING.md
+8-26
Original file line number
Diff line number
Diff line change
@@ -4,39 +4,21 @@ Releasing checklist:
4
4
5
5
(1) Write a changelog.
6
6
7
-
(2) Make sure to update SPDX license identifiers. For example:
7
+
(2) Checkout the branch to be released. This should be `main` except in the event of a hotfix. For hotfixes, checkout the latest release branch.
8
8
9
-
```cairo
10
-
# SPDX-License-Identifier: MIT
11
-
# OpenZeppelin Contracts for Cairo v0.1.0 (account/Account.cairo)
12
-
```
13
-
14
-
to
15
-
16
-
```cairo
17
-
# SPDX-License-Identifier: MIT
18
-
# OpenZeppelin Contracts for Cairo v0.2.0 (account/Account.cairo)
19
-
```
20
-
21
-
(3) Update documentation version in `docs/antora.yml`
22
-
23
-
```diff
24
-
name: cairo-contracts
25
-
title: Contracts for Cairo
26
-
-version: 0.1.0
27
-
+version: 0.2.0
28
-
(...)
29
-
```
30
-
31
-
(4) Create a release branch and add a tag to it. This branch can be useful if we need to push a hot fix on top of an existing release in the case of a bug.
9
+
(3) Create a tag for the release.
32
10
33
11
```sh
34
-
git checkout -b release-0.2.0
35
12
git tag v0.2.0
36
13
```
37
14
38
-
(5) Push the tag to the main repository, [triggering the CI and release process](https://github.com/OpenZeppelin/cairo-contracts/blob/b27101eb826fae73f49751fa384c2a0ff3377af2/.github/workflows/python-app.yml#L60).
15
+
(4) Push the tag to the main repository, [triggering the CI and release process](https://github.com/OpenZeppelin/cairo-contracts/blob/b27101eb826fae73f49751fa384c2a0ff3377af2/.github/workflows/python-app.yml#L60).
39
16
40
17
```sh
41
18
git push origin v0.2.0
42
19
```
20
+
21
+
Note that the CI automatically:
22
+
23
+
- Updates the SPDX identifiers and antora.yml versions with the pushed tag
24
+
- Creates a release branch and adds a tag to it. This can be useful if we need to push a hot fix on top of an existing release in the case of a bug.
0 commit comments