@happy-kitchen-89482 @curved-manchester-66006 Do we have a convention for creating an alpha release, without pushing a branch to main? I want to chicken and egg Pants-Python 314 with scie-pants - through all the testing I've done locally, it works - and any workarounds I can come up with to setup a similar environment sorta work around any of my concerns for the test itself. e.g. Will scie-pants correctly pull Python 3.14 from our pants repo based on a certain version

I don't think so. An alpha release implies cutting a new version, with new notes etc.

So, I've tested it independently, and I would like to follow the existing convention for tests in scie-pants (for better or worse) before we cut an official scie-pants, but that assumes the pants stuff is built and available in a repo too. I can workaround all these problems, do intermediate builds pointing elsewhere, and fix them later too. But was hoping to follow a singular release process as possible