solving the test.pypi release issue

[mohammadamint]

To make the test.pypi Action work, the first release should be done manually, to get the API Token.

The API Token needs to be updated accordingly.

[FLomb]

This was addressed by PR #97

[Bachibouzouk]

It seems the automatic push on test_pypi fails because of authentification problems

Error: Trusted publishing exchange failure: 
OpenID Connect token retrieval failed: GitHub: missing or insufficient OIDC token permissions, the ACTIONS_ID_TOKEN_REQUEST_TOKEN environment variable was unset

The workflow context indicates that this action was called from a
pull request on a fork. GitHub doesn't give these workflows OIDC permissions,
even if `id-token: write` is explicitly configured.

To fix this, change your publishing workflow to use an event that
forks of your repository cannot trigger (such as tag or release
creation, or a manually triggered workflow dispatch).

[Bachibouzouk]

@mohammadamint can you have a look at this?

[Bachibouzouk]

@FLomb - I reopened this issue concerning the test-pypi issue. It is probably due to the 2FA now enforced on pypi/test-pypi

[mohammadamint]

@mohammadamint can you have a look at this?

Sorry @Bachibouzouk I was out for a couple of days. I will take a look to it by the end of the day of it is ok. In case it is urgent, we can probably ignore the issue

[Bachibouzouk]

https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

[mohammadamint]

https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

Hi Pierre,

SOrry for the late reply. I am in a long mission to Africa, and very bad internet access. I will solve this issue as soon as I come back to normal life!