Create another PyPI release

[criver]

What's the problem this feature will solve?

The 7.4.1 version has a bug in generating NoCandidateFound error message. It says the InstallCandidate is not comparable. It seems to be fixed in the github since there is a key operator added to the line of the code.

Describe the solution you'd like

Alternative Solutions

Additional context

[chrysle]

We hope to do so soon, but are currently blocked by rather tricky CI issues and have a few elements on our feature queue.

[pohmelie]

Any news about release? I need too with #204 fixed.

[hugovk]

We're using pip-tools to help manage the CPython release automation (https://github.com/python/release-tools), and we're waiting for a release of #2082 / #2081.

cc the project leads from https://jazzband.co/projects/pip-tools:

@davidovich @vphilippon @atugushev Is there anything in particular you need help with before we can make the next release? If it's lack of time, would it help finding another project lead to be able to make releases?

Thank you!

[hugovk]

Hmm, the daily cron has been failing for the past 7 months, for both latest and previous versions of pip:
https://github.com/jazzband/pip-tools/actions/workflows/cron.yml

So that's the first thing that needs addressing.

It's things like this, so possibly a change in tooling rather than in pip internals:

  -     #   -c constraints.txt
  +     #   -c /tmp/tmpejmx42yt/constraints.txt

[webknjaz]

@hugovk FYI, I'm looking into the CI stuff today and already have some idea of the changes I want to make.

[webknjaz]

Here's my plan: #2140

[webknjaz]

xref #2147

[webknjaz]

FTR, this may require @jezdez's involvement if no leads materialize in here… Meanwhile, I've pinged him regarding the Trusted Publishing initiative in other issues.