[Automated] Merge release into main

[ProKil]

Automated Pull Request.

This PR also pins mypy version to avoid its latest bug. python/mypy#17543

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.78%. Comparing base (701f2a8) to head (e4f0a26).
Report is 7 commits behind head on main.

@@            Coverage Diff             @@
##             main     #146      +/-   ##
==========================================
- Coverage   61.71%   60.78%   -0.93%     
==========================================
  Files          55       55              
  Lines        2714     3295     +581     
==========================================
+ Hits         1675     2003     +328     
- Misses       1039     1292     +253     

see 7 files with indirect coverage changes

[XuhuiZhou]

I thought 1.11.0 is the buggy version?

[ProKil]

so <1.11.0 is the right range.

[XuhuiZhou]

what does this do? I thought the main should be the most updated branch? Or it's more like the release branch simply changes the version name?

[ProKil]

We can use a different model, but I am using the following method:

1. Our main branch is the develop branch, which accepts reviewed PRs (feature/bug fix). Nobody can push anything to main directly without a PR;
2. When main branch has enough features for a new release, a release branch is created. After minimal preparation, e.g. bumping versions, CHANGELOG, etc., the core maintainers push a tag to release, which submits the package to PyPI;
3. after the release branch is tagged, we should merge the release branch back to master (which was not automated previously, but this PR automates this process).

i.e. main has the latest features, release branch is for preparation for a release. Since we strictly ban direct commits to main, the tags are pushed to release.

[XuhuiZhou]

Cool, thanks for the explanation! I think this is worthwhile to add to the contribution doc, which I will do that.

[XuhuiZhou]

Cool, thanks for the explanation! I think this is worthwhile to add to the contribution doc, which I will do that.