gh-action-pypi-publish: `invalid-publisher`: valid token, but no corresponding publisher

Hi, I have a release workflow which suddenly stopped working:

First run worked
Second run failed because I tried to upload the same version number by accident
Third run for a new version number shows invalid-publisher: valid token, but no corresponding publisher

Aside the version numbers I did not change anything. I also tried to remove the trusted publisher and add it again and rerun the action but still no success.

What could be the reason that this worked the first time but not since then?

About this issue

Original URL
State: closed
Created a year ago
Comments: 61 (40 by maintainers)

Most upvoted comments

Doing nothing? Yeah I think I can handle that 😄

eifinger on Aug 9, 2023

It was from a clean run initially. Had not run since a month or so back.

Got it, thanks for confirming. Could you humor me and try it again from a clean run? I don’t expect it to change, but just for an additional datapoint 🙂

Will try with a new release later today.

eifinger on Aug 9, 2023

Thanks everyone! The README update with the link merged.

webknjaz on Aug 11, 2023

If you have time, this would be welcome. Meanwhile, I released v1.8.10 with the hotfix.

webknjaz on Aug 10, 2023

My bug, sorry. Fixing now.

Looks like we need to start having pytest-based tests too…

webknjaz on Aug 10, 2023

My bug, sorry. Fixing now.

woodruffw on Aug 10, 2023

I’ve also opened #174 with some changes that should assist in debugging here: if you configure your publishing workflow to use that branch rather than the normal release, it should give us some additional context here slightly_smiling_face

Released in v1.8.9

webknjaz on Aug 10, 2023

Not sure that tracks, because https://github.com/eifinger/pywaze/actions/runs/5794194719/job/15703309543 was the first attempt for that run, and it failed the same way.

di on Aug 9, 2023

I’ve also opened https://github.com/pypa/gh-action-pypi-publish/pull/174 with some changes that should assist in debugging here: if you configure your publishing workflow to use that branch rather than the normal release, it should give us some additional context here 🙂

woodruffw on Aug 9, 2023

The only thing that changed is that this was likely converted from a pending publisher to a regular publisher, so something doesn’t agree in the publisher queries/verification between the two.

I’m working on adding some better error messages here (there are a lot of failure modes that would result in this one error message) which should at least help narrow this down.

di on Aug 8, 2023