Skip to content

Commit cfcc081

Browse files
authored
Release instructions (#150)
1 parent f034c96 commit cfcc081

File tree

1 file changed

+28
-22
lines changed

1 file changed

+28
-22
lines changed

docs/contribute.md

Lines changed: 28 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -30,29 +30,35 @@ nox -s docs -- live
3030

3131
The easiest way to make a release is to follow these steps:
3232

33-
1. **Bump the version in `__init__.py` and push it to main**.
34-
We try to use [semver version numbers](https://semver.org/) but don't stress out about it too much.
35-
- In your commit message use something like `RLS: vX.Y.Z`.
36-
- Add a changelog to `CHANGELOG.md`[^1].
37-
2. **Draft a new release on GitHub**.
38-
Under the [`releases` page](https://github.com/executablebooks/github-activity/releases) click [the `Draft a New Release` button](https://github.com/executablebooks/github-activity/releases/new).
39-
- Connect the release to your release commit.
40-
- Create a new tag for the release called `vX.Y.Z`.
41-
- The name of the release is also `vM.m.p`.
42-
- Re-paste your changelog here as well if you like.
43-
3. **Publish the release**.
44-
When you hit `Publish release`, a GitHub action will trigger that runs our tests, and then publishes the latest tag to PyPI if the tests pass.
45-
That's it, you're done!
33+
1. **Install `tbump`**:
34+
35+
```
36+
pip install tbump
37+
```
38+
39+
1. **Bump the version**:
40+
41+
```
42+
tbump NEW_VERSION
43+
```
4644

47-
[^1]: To add a changelog with `github-activity`, run something like:
45+
Then follow the prompts.
4846

49-
```bash
50-
github-activity -s <LAST-TAG> -o tmp.md
51-
```
47+
This will bump the appropriate locations, make a release commit, and push the tag to GitHub.
5248

53-
Then copy the contents of `tmp.md` and paste it into our changelog, bumping section header levels if needed.
54-
Alternatively, use `nox`:
49+
1. **Generate a changelog for the new version**:
5550

56-
```bash
57-
nox -s changelog
58-
```
51+
```
52+
github-activity -s [old-tag] -u [new-tag]
53+
```
54+
55+
We will paste this into the GitHub release.
56+
57+
1. **Draft a new release on GitHub**.
58+
Under the [`releases` page](https://github.com/executablebooks/github-activity/releases) click [the `Draft a New Release` button](https://github.com/executablebooks/github-activity/releases/new).
59+
- Connect the release to the tag you just pushed.
60+
- The name of the release is also `tag-name`.
61+
- Paste your changelog here.
62+
1. **Publish the release**.
63+
When you hit `Publish release`, a GitHub action will trigger that runs our tests, and then publishes the latest tag to PyPI if the tests pass.
64+
That's it, you're done!

0 commit comments

Comments
 (0)