New release about async-lru

[Dreamsorcerer]

@webknjaz Do you have any idea what's happening? The deploy pipeline succeeds, but there's no release on PyPI...

[webknjaz]

Yes: 37a63ee#r120964491.

[webknjaz]

This is when the PyPI API token stopped being passed: 00a0fb0#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fL124.
It'll work again once you complete the configuration of the CI workflow to actually make use of secretless publishing.

[webknjaz]

Oh... the workflow name is also slightly different.

[webknjaz]

@Dreamsorcerer you can re-try triggering publishing now.

[webknjaz]

@Dreamsorcerer I made the configuration and dropped the secrets on GitHub, you still need to revoke that API token in your PyPI account. I'll leave the release to you now.

P.S. There's a possibility that the permissions are now too restrictive. If the GH release update step fails, you'll probably need to add contents: write and restart.

[Dreamsorcerer]

OK, sorted. Thanks.

[webknjaz]

Release: https://pypi.org/project/async-lru/2.0.3/.

[webknjaz]

OK, sorted. Thanks.

Did you revoke the PyPI API token on your side?

[Dreamsorcerer]

Yeah, trying. PyPI seems bugged and won't delete right now.

[webknjaz]

Well, if you didn't store it elsewhere, it's safe to postpone and try later, I suppose.