Release 1.7.4

[nicoddemus]

No description provided.

[nicoddemus]

@RonnyPfannschmidt I don't have admin access to PyPI, could you please setup trusted publishing, using the deploy workflow? Thanks

[nicoddemus]

@RonnyPfannschmidt did you setup trusted publishing?

[RonnyPfannschmidt]

Not that I remember

I can check later

[nicoddemus]

Thanks, please see #104 (comment).

[RonnyPfannschmidt]

configured

[nicoddemus]

Hmm failing with:

  Token request failed: the server refused the request for the following reasons:
  
  * `invalid-publisher`: valid token, but no corresponding publisher (Publisher with matching claims was not found)
  
  This generally indicates a trusted publisher configuration error, but could
  also indicate an internal error on GitHub or PyPI's part.
  
  
  The claims rendered below are **for debugging purposes only**. You should **not**
  use them to configure a trusted publisher unless they already match your expectations.
  
  If a claim is not present in the claim set, then it is rendered as `MISSING`.
  
  * `sub`: `repo:pytest-dev/pytest-forked:ref:refs/tags/v1.7.5`
  * `repository`: `pytest-dev/pytest-forked`
  * `repository_owner`: `pytest-dev`
  * `repository_owner_id`: `8897583`
  * `workflow_ref`: `pytest-dev/pytest-forked/.github/workflows/deploy.yml@refs/tags/v1.7.5`
  * `job_workflow_ref`: `pytest-dev/pytest-forked/.github/workflows/deploy.yml@refs/tags/v1.7.5`
  * `ref`: `refs/tags/v1.7.5`
  * `environment`: `MISSING`

Would you mind adding me as maintainer on PyPI? Then I can debug the configuration myself.

[RonnyPfannschmidt]

added core as owners

[RonnyPfannschmidt]

I had a typo in the repo name

[webknjaz]

environment: MISSING

@nicoddemus hey, I always recommend having the environment set to pypi (and then adding an additional approval protection in the repo settings for it, FYI).

[nicoddemus]

True, done: #105