chore: release version 1.1.9 (#316)

* ci: prepare support for python 3.12

* chore: run coverage with python 3.10

build: use latest gha version (#300)

ci(docs): fix the doc publishing job (#261)

* ci(docs): fix the doc publishing job

* ci(docs): put dependency in setup.cfg

ci: remove coverage from the wheel testing process (#229)

* test: move cov option in gh action

* ci: remove cov in wheel testing

* test: adding --cov flag

chore: pre-commit autoupdate (#212)

updates:
- [github.com/psf/black: 21.8b0 → 21.9b0](psf/black@21.8b0...21.9b0)

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

ci(changelog): add ci in Maintenance section (#170)

ci: use joerick/[email protected] action in upload to pypi (#120)

* ci: use cibuildwheel action in upload to pypi

* ci(pypi-upload): Using checkout@v1 is easier

than v2 if you use setuptools_scm.

* ci: remove useless option from actions/checkout@v1

* ci: try with CIBW_ENVIRONMENT

* ci: remove duplicate variable definition

* ci: checkout@v1 is better with setuptools_scm

* ci: must keep SETUPTOOLS_SCM_PRETEND_VERSION

twice because sdist needs it.

chore: release version 1.1.2 (#90)

build(pypi): new version 1.1.1 (#86)

No change to the code compared to the previous version.
The package was only partly published to Pypi because of the failure of one provider in the CI.
Since Pypi's policy prevents re-uploading twice the same version, we have to increment the version number.

* build(pypi): new version 1.1.1

* ci: remove temporary gh action

This job was introduced for testing purposes only.

* docs(changelog): update changelog

* ci(pypi): change python version 3.7-->3.8

No need to have two different python versions in
the same gh action.

* ci(pypi): use a release candidate to test the ci

Make sure that the publishing process to
pypi finishes completely.
We use a 1.1.1rc1 as a version number.

* ci(pypi): new version 1.1.1

chore(tag): add tag v1.1.0