COM-14701 - Release 0.7.1

[rsanchez87]

No description provided.

[rgonzalezfluendo]

should we merge v0.7.0 in master first?

[rsanchez87]

should we merge v0.7.0 in master first?

No, let's skip merging v0.7.0 into master.

The release was yanked on PyPI due to a missing sdist caused by a CI issue (Python 3.7 not supporting setuptools>=69, which is required for correct sdist filename normalization).

https://github.com/fluendo/fluster/actions/runs/24830781578

We're going straight to v0.7.1 with the fix included here.

The v0.7.0 branch has been deleted.

[mdimopoulos]

should we merge v0.7.0 in master first?

No, let's skip merging v0.7.0 into master.

The release was yanked on PyPI due to a missing sdist caused by a CI issue (Python 3.7 not supporting setuptools>=69, which is required for correct sdist filename normalization).

https://github.com/fluendo/fluster/actions/runs/24830781578

We're going straight to v0.7.1 with the fix included here.

The v0.7.0 branch has been deleted.

Does this mean that we should change minimum python version from 3.7 to 3.8 in the documentation? Or is this only a build-time dependency?

[rsanchez87]

should we merge v0.7.0 in master first?

No, let's skip merging v0.7.0 into master.
The release was yanked on PyPI due to a missing sdist caused by a CI issue (Python 3.7 not supporting setuptools>=69, which is required for correct sdist filename normalization).
https://github.com/fluendo/fluster/actions/runs/24830781578
We're going straight to v0.7.1 with the fix included here.
The v0.7.0 branch has been deleted.

Does this mean that we should change minimum python version from 3.7 to 3.8 in the documentation? Or is this only a build-time dependency?

It's only a build dependency in the CI