blob: 1646e42fc3a00ee7275f5a5d62f852b5ebd03dfe (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
# Releasing an astroid version
So, you want to release the `X.Y.Z` version of astroid ?
## Process
(Consider triggering the "release tests" workflow in GitHub Actions first.)
1. Check if the dependencies of the package are correct
2. Check the result (Do `git diff vX.Y.Z-1 ChangeLog` in particular).
3. Install the release dependencies `pip3 install pre-commit tbump`
4. Bump the version and release by using `tbump X.Y.Z --no-push`.
5. Push the tag.
6. Release the version on GitHub with the same name as the tag and copy and paste the
appropriate changelog in the description. This trigger the pypi release.
## Post release
### Back to a dev version
Move back to a dev version with `tbump`:
```bash
tbump X.Y.Z+1-dev0 --no-tag --no-push # You can interrupt during copyrite
git commit -am "Upgrade the version to x.y.z+1-dev0 following x.y.z release"
```
Check the result and then upgrade the main branch
### Milestone handling
We move issue that were not done in the next milestone and block release only if it's an
issue labelled as blocker.
## Post release
### Merge tags in main for pre-commit
If the tag you just made is not part of the main branch, merge the tag `vX.Y.Z` in the
main branch by doing a history only merge. It's done in order to signal that this is an
official release tag, and for `pre-commit autoupdate` to works.
```bash
git checkout main
git merge --no-edit --strategy=ours vX.Y.Z
git push
```
|
