Upload wheels to scientific-python-nightly-wheels index

[lysnikolaou]

Related to #8199.

In order for this to work we're going to need a secret named PILLOW_NIGHTLY_UPLOAD_TOKEN. @hugovk Did you already create it? If so, what's its name?

[radarhere]

Your original idea was ANACONDA_ORG_UPLOAD_TOKEN, and that was what he requested of aclark4life

[lysnikolaou]

Thanks for the pointer @radarhere! Updated now.

[radarhere]

For my curiosity - can this be removed once Python 3.13 final is released on October 1?

[lysnikolaou]

Hmm, that's a good question. Many people will start testing only after the final release, so we'll have free-threading-related bugfixes after that as well, and nightlies will continue to be helpful then. So my feeling is that we can go on uploading nightlies after final and only stop when threading-related bug reports start slowing down significantly. What do you think?

[hugovk]

The wheels build takes up a fair amount of CI time/runners.

@radarhere Is 01:42 UTC going to interfere with when you're active? We can move it to your night/inactive time if you like.

[radarhere]

Thanks for the thought, but that's not a problem for me personally - especially since d83c7b3 skips the aarch64 jobs.

[hugovk]

Hmm, that's a good question. Many people will start testing only after the final release, so we'll have free-threading-related bugfixes after that as well, and nightlies will continue to be helpful then. So my feeling is that we can go on uploading nightlies after final and only stop when threading-related bug reports start slowing down significantly. What do you think?

Yes, I think it will be helpful too.

[aclark4life]

Your original idea was ANACONDA_ORG_UPLOAD_TOKEN, and that was what he requested of aclark4life

Will do! Stay tuned …

[aclark4life]

@hugovk And … can't find my secret key or emergency kit, can you please start a recovery for me and I'll be sure to save this time? Sorry about that.

[hugovk]

Done!

Recovery started, pending action by Jeffrey A. Clark.

[aclark4life]

Done!

Recovery started, pending action by Jeffrey A. Clark.

Thanks, also done! Do we still need any/all of the other secrets ?

I have an Anaconda Cloud account too: https://anaconda.org/aclark

[radarhere]

CODECOV_ORG_TOKEN, yes.

Pillow/.github/workflows/test.yml

Line 163 in 86f4cfb

token: ${{ secrets.CODECOV_ORG_TOKEN }}

TIDELIFT_API_KEY was added for #5762 (comment). We don't need it anymore as of #6739

GH_PAT was added for #4071 (comment), which I don't think ever materialised.

[radarhere]

I reran the wheels job thinking it would make use of the new secret, but I forgot that it was only used by workflow dispatch and schedule.

I guess merging and seeing if this works is the next step.

[hugovk]

Let's try it!

Edit: manually triggered: https://github.com/python-pillow/Pillow/actions/runs/9975952588

[lysnikolaou]

It seems that the QEMU job was started as well. Opened #8243 to fix that. Does it make sense to stop everything and rerun it after that follow-up PR has been merged as well?

[hugovk]

Yes, let's save two hours of CI time, I've cancelled it.

[hugovk]

#8243 is merged, here's a new run: https://github.com/python-pillow/Pillow/actions/runs/9978963564

[radarhere]

Fyi, our authentication token expired - https://github.com/python-pillow/Pillow/actions/runs/16675133594/job/47205371948#step:3:208

Error: ('Authentication token has expired', 401)

I've generated a new token at anaconda.org and updated the secret in GitHub.