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
Update RELEASING.md to match the new Tuist setup (#596)
Updated `RELEASING.md` based on our conversation from today. Not
updating the release script just yet as we are looking to remove
`CHANGELOG.md` completely in favour of conventional commits.
I also created a GitHub
[release](https://github.com/square/Listable/releases/tag/16.4.0) for
the latest version based on our conversation.
### Checklist
Please do the following before merging:
- [x] Ensure any public-facing changes are reflected in the
[changelog](https://github.com/square/Listable/blob/main/CHANGELOG.md).
Include them in the `Main` section.
Earlier releases were ad-hoc and not tracked. To see all changes, please reference [closed PRs on Github](https://github.com/kyleve/Listable/pulls?q=is%3Apr+is%3Aclosed).
Copy file name to clipboardExpand all lines: RELEASING.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,11 +6,7 @@
6
6
7
7
1. Update localized strings. Find the sha of the latest commit with `git log`, then run `./Scripts/install_localized_strings.sh [sha]` to download the latest translations.
8
8
9
-
1. Update the library version in `version.rb` if it has not already been updated (it should match the version number that you are about to release).
10
-
11
9
1. Update `CHANGELOG.md` (in the root of the repo), moving current changes under `Main` to a new section under `Past Releases` for the version you are releasing.
12
-
13
-
The changelog uses [reference links](https://daringfireball.net/projects/markdown/syntax#link) to link each version's changes. Remember to add a link to the new version at the bottom of the file, and to update the link to `[main]`.
14
10
15
11
1. Re-generate the documentation.
16
12
```bash
@@ -19,14 +15,15 @@
19
15
20
16
1. Commit the version bumps and doc changes.
21
17
```bash
22
-
git commit -am "Bumping versions to 0.1.0."
18
+
git commit -am "Bumping version to 0.1.0"
23
19
```
24
20
25
21
1. Push your branch and open a PR into `main`.
26
22
27
-
1. Once the PR is merged, fetch changes and tag the release, using the merge commit:
28
-
```bash
29
-
git fetch
30
-
git tag 0.1.0 <merge commit SHA>
31
-
git push origin 0.1.0
32
-
```
23
+
1. Go to the [Releases](https://github.com/square/Listable/releases) and `Draft a new release`.
24
+
25
+
1. In the release notes, copy the changes from the changelog.
26
+
27
+
1. Ensure the `Title` corresponds to the version we're publishing.
0 commit comments