[CI] Modern Release Workflow

[leycec]

@tusharsadhwani: You are amazing! Because you are amazing, I regret bothering you. Yet, I must bother you. @bollwyvl noted at PR #1 that ipython-beartype currently lacks published tarballs on PyPI, which then prevents @bollwyvl from packaging ipython-beartype via conda-forge:

Also, of note: would love to ship this for conda-forge, but would ideally be able to use one of the following for building from source:

• a source distribution .tar.gz on PyPI (preferred by most downstreams)
• a tag here on GitHub

Ideally, both ipython-beartype and pytest-beartype would leverage a modern GitHub Actions-based release workflow. @beartype does this by automatically publishing a new release to PyPI whenever a new tag prefixed by the letter "v" (e.g., v0.1.0, v1.2.3) is pushed to the @beartype repo.

Would you mind copy-pasting @beartype's .github/workflows/python_release.yml file into both ipython-beartype and pytest-beartype when you find a scarce moment in your amazing life full of fun, sun, dangerously spicy curry, and outrageous software productivity in Bengaluru?

You are now thinking...

What's The Catch? There's Always a Catch with @leycec

...yeah. There's a catch. PyPI really wants everyone to start doing this Trusted Publisher thing. So, @beartype's .github/workflows/python_release.yml assumes that you've done this Trusted Publisher thing. I'm so sorry. I have burdened you with bureaucracy. 😭

It's a bit annoying to set all of this up the first time around – but ultimately saves a ton of development time. I've published quite a few @beartype releases with this workflow now. It just works, which is more than I can say for how I used to publish @beartype. Those were dark days. 😆

Please take your leisurely time. Thanks again, @tusharsadhwani! You amaze me. I bow before you. 🙇

[tusharsadhwani]

I do want to learn (and switch to) Trusted publishing for my personal projects as well, so I'm happy to pick this up. Good timing on your part (;

[leycec]

Phenomenal. And... I'm still stunned at how fast you respond on GitHub. I'm pretty sure that's 0-minute turn-around. How? How do you respond instantaneously!? It's almost like... telepathy. Like, your hands aren't even moving on the keyboard. Yet, messages are being written. Please teach me your dark secrets! 🙏

[leycec]

@ntjohnson1's glorious work at #4 puts us a lot closer to a modern release workflow. The only remaining puzzle pieces left are to:

1. Enable PyPI Trusted Publishers for this repo.
2. Define a new .github/workflows/release.yml workflow based on PyPI Trusted Publishers.

Let's see if anybody does anything. It's been a baking hot summer and I for one could use a shower. 😓

[tusharsadhwani]

I'm on semi-vacation in the States, working a full time job, enjoying the nice views and parks in SF and finding it very hard to do any other work. I'll get to this someday, surely.

[leycec]

Oh, ho! What fantastic news. The Bay Area rocks. That was a dumb pun, because Alcatraz... The Rock... Anyways. So glad you landed in Silicon Valley. Have a great time! I sure did. The opportunities are boundless and the venture capital flows like spiced honey wine. Of course, the working hours can be a bit grueling. Oh, Gods. The working hours. The death march! The crunch mode! I shudder and so do my wrists. Still, I am unsurprised you made it at last. The Land of Milk and Honey awaits – and joy will surely follow.

In the meanwhile, don't sweat the open-sourcing. I'll happily pick up the slack. When you live in a cabin in the woods, free time is the one thing you have in copious abundance. 😂

[leycec]

Actually, I do have one final request. I know you're super-busy. I know you have much better things to do. Vacation is precious. The Bay Area is calling. But...

I need PyPI access to both pytest-beartype and ipython-beartype so that I can enable Trusted Publishers. Thankfully, this should be super-easy on your end. I promise! Five minutes of your precious time. That's all I ask. Just:

1. Login to PyPI.

2. Click the ⬇️ arrow to the right of your profile picture in the upper right-hand corner.

3. Click Your projects.

4. Click the SOLE OWNER link next to both pytest-beartype and ipython-beartype.

5. Scroll down to Invite collaborator.

6. Under User, enter:

   leycec

7. Under Role, select Owner.

That's it! Thanks so much for this one last action item. I'm so sorry for intruding on your vacation. In hindsight, I should have just created and maintained these repos. It was too much to ask. This is all my fault, @tusharsadhwani. 😮‍💨

[tusharsadhwani]

Oh no problems. I enjoy maintaining projects, and although I have been out of shape lately, hopefully haven't been too negligent just yet 🤓

I've added you as co owners to both projects

[leycec]

Thanks so much for humoring this middle-aged bald man in a cabin one last time. 😅

You're not out of shape at all – and you're certainly not negligent. You're young (which is so exciting), you're on vacation (which is even more exciting), and you're somehow even working while on vacation (which... is definitely a thing).

I wish you all the best in life. You will achieve all your dreams.

[leycec]

Resolved by 1a3074d. PyPI Shangri-La is now in sight. 🧗 🗻 🛕

ipython-beartype now sports a spiffy new GitHub Actions-based continuous integration (CI) workflow for automating new PyPI (and hopefully soon conda-forge) releases from published git tags. This workflow leverages PyPI's new Trusted Publishers secrecy model. Naturally, I stole everything from the @beartype codebase. In theory, ipython-beartype should now look less sketchy to prospective users on PyPI. In practice, everything will blow up, because everything always blows up. Curse you, Murphy and your Law!

ipython-beartype currently lacks published tarballs on PyPI, which then prevents @bollwyvl from packaging ipython-beartype via conda-forge. This resolution should resolve these critical blockers. Our upcoming ipython-beartype 0.2.0 release should now automatically publish tarballs to PyPI, paving for the way for an official conda-forge-hosted feedstock.

Let us do this, fam. Finally. Something good happened on a Saturday night.