DuniterPy issueshttps://git.duniter.org/clients/python/duniterpy/-/issues2024-01-29T10:42:03+01:00https://git.duniter.org/clients/python/duniterpy/-/issues/210Set up release feature from gitlab-ci2024-01-29T10:42:03+01:00MoulSet up release feature from gitlab-ci- https://docs.gitlab.com/ee/ci/yaml/#release
- https://docs.gitlab.com/ee/user/project/releases/release_cicd_examples.html
```yaml
release_job:
stage: package
image: registry.gitlab.com/gitlab-org/release-cli:latest
rules:
- ...- https://docs.gitlab.com/ee/ci/yaml/#release
- https://docs.gitlab.com/ee/user/project/releases/release_cicd_examples.html
```yaml
release_job:
stage: package
image: registry.gitlab.com/gitlab-org/release-cli:latest
rules:
- if: $CI_COMMIT_TAG
script:
- echo "running release_job"
release:
tag_name: '$CI_COMMIT_TAG'
description: '$CI_COMMIT_TAG'
```
- [ ] Fix current releases
- [ ] Add missing releases
- https://git.duniter.org/clients/python/duniterpy/-/releases1.3.0https://git.duniter.org/clients/python/duniterpy/-/issues/208Add support for Python v3.132023-11-20T14:27:29+01:00MoulAdd support for Python v3.13### Python pre-releases
- [ ] Set up v3.13 test job
- [ ] With `allow_failure: true`, to allow tests to fail
### Python stable release
- [ ] Remove `allow_failure: true`, now on the tests should pass
- [ ] Move coverage to v3.13 job
-...### Python pre-releases
- [ ] Set up v3.13 test job
- [ ] With `allow_failure: true`, to allow tests to fail
### Python stable release
- [ ] Remove `allow_failure: true`, now on the tests should pass
- [ ] Move coverage to v3.13 job
- [ ] Set default container used by jobs to v3.13
- [ ] Handle deprecation warning and breaking features
### Post
- [ ] Open follow-up v3.14 tickets
### References
- Expected to be release the [October 1st 2024](https://peps.python.org/pep-0719/).
- docker/python3/poetry#10+1.3.02024-10-01https://git.duniter.org/clients/python/duniterpy/-/issues/199Drop Python v3.8 support2023-05-18T16:05:59+02:00MoulDrop Python v3.8 support### Date when Python project won’t support v3.8
- [Python 3.8 support will be dropped in October 14th of 2024](https://devguide.python.org/versions/) [[1](https://endoflife.date/python)]
- [Platform which still uses Py3.8](https://repolo...### Date when Python project won’t support v3.8
- [Python 3.8 support will be dropped in October 14th of 2024](https://devguide.python.org/versions/) [[1](https://endoflife.date/python)]
- [Platform which still uses Py3.8](https://repology.org/badge/vertical-allrepos/python.svg)
## Todos
### DuniterPy
- [ ] `pyproject.toml`: Bump minimum versions:
- [ ] `tools.poetry.dependency.python`
- [ ] `tools.ruff.target-version`
- [ ] Delete test job for v3.8 from `.gitlab-ci.yml`
- [ ] Update minimal version in documentation: `README.md` and `docs/index.rst`
### Container
- [ ] Delete v3.8 Docker image generation
---
- [ ] Create ticket for Py3.9Backlog2024-10-14https://git.duniter.org/clients/python/duniterpy/-/issues/198Introduce ruff pre-commit hook2023-07-04T20:11:32+02:00MoulIntroduce ruff pre-commit hook- [x] Get rid of `isort`, `pylint`, `pyupgrade` pyproject, pre-commit, gitlab-ci configurations
- [x] Introduce `ruff` pyproject, pre-commit, gitlab-ci configurations
- [ ] `Makefile`: replace `pylint` with `ruff` (to be honest, I don’t ...- [x] Get rid of `isort`, `pylint`, `pyupgrade` pyproject, pre-commit, gitlab-ci configurations
- [x] Introduce `ruff` pyproject, pre-commit, gitlab-ci configurations
- [ ] `Makefile`: replace `pylint` with `ruff` (to be honest, I don’t see the point of make rules for pre-commit hooks).
- [ ] Fix `ruff` reports
- [ ] Use `pathlib`
- [ ] #200+
- [ ] Update hooks used in `CONTRIBUTING.md` § pre-commit1.3.0MoulMoulhttps://git.duniter.org/clients/python/duniterpy/-/issues/195Fix coverage integration into GitLab2023-06-04T13:21:49+02:00MoulFix coverage integration into GitLabThe tests coverage integration into GitLab is no longer working since [it support changed from GitLab v15.0](https://docs.gitlab.com/ee/ci/pipelines/settings.html#merge-request-test-coverage-results).
The regex is no longer configured i...The tests coverage integration into GitLab is no longer working since [it support changed from GitLab v15.0](https://docs.gitlab.com/ee/ci/pipelines/settings.html#merge-request-test-coverage-results).
The regex is no longer configured into the project settings but in `.gitlab-ci.yml`
### Acceptance criteria
- [x] Fix coverage percentage integration into GitLab using this [regex](https://forum.gitlab.com/t/python-coverage-always-unknown/47819/3)
- [x] [Integrate coverage report into GitLab](https://docs.gitlab.com/ee/ci/testing/test_coverage_visualization.html#python-example)1.3.0https://git.duniter.org/clients/python/duniterpy/-/issues/184Autodoc: support for dev doc and stable/release doc2021-07-21T16:32:52+02:00MoulAutodoc: support for dev doc and stable/release doc- [ ] Move the documentation publication stage before the release stage, the release job are blocking the doc generation. Most likely !158 is enough.
- [ ] On the `main` branch, without tag, allow to trigger the doc job at every commit o...- [ ] Move the documentation publication stage before the release stage, the release job are blocking the doc generation. Most likely !158 is enough.
- [ ] On the `main` branch, without tag, allow to trigger the doc job at every commit on `main` or `dev` path, for the job to not get rusted
- [ ] On the `main` branch, with a tag, publish to the `$version` path
This is the case with https://click.palletsprojects.comBackloghttps://git.duniter.org/clients/python/duniterpy/-/issues/167Deploy and serve coverage report web page via GitLab Pages2023-07-07T20:32:36+02:00MoulDeploy and serve coverage report web page via GitLab PagesCurrently, GitLab Pages is used to serve the auto generated Sphinx documentation.
We should find and decide for a solution to distribute the documentation and the test coverage report in parallel.
Something like:
- https://clients.page...Currently, GitLab Pages is used to serve the auto generated Sphinx documentation.
We should find and decide for a solution to distribute the documentation and the test coverage report in parallel.
Something like:
- https://clients.pages.duniter.org/python/duniterpy/doc/index.html
- https://clients.pages.duniter.org/python/duniterpy/test/index.html
Or, even better:
- https://py.duniter.org or https://duniterpy.duniter.org
- https://clients.pages.duniter.org/python/duniterpy/index.html1.3.0