Open elmsdata opened 1 year ago
@elmsdata I provisioned the cdevents-bot account, configured 2FA and added the details to 1password.
I provisioned an API token and stored it in the PYPI_BOT_TOKEN
secret, so that it's available to GitHub actions.
As I'm sure you're aware, the link you provided pointed to the test instance of pypi. Once the release process is confirmed to be working fine we shall create an account in the production instance of pypi and update the API token.
@elmsdata I provisioned the cdevents-bot account, configured 2FA and added the details to 1password. I provisioned an API token and stored it in the
PYPI_BOT_TOKEN
secret, so that it's available to GitHub actions.As I'm sure you're aware, the link you provided pointed to the test instance of pypi. Once the release process is confirmed to be working fine we shall create an account in the production instance of pypi and update the API token.
Wonderful, thank you @afrittoli for setting that up quickly! Working on an incremental process so we don't push incorrectly to the pypi, so once everything is set we will be good for production instance!
Will now work on the github automation to push to the pypi!
In preparation for releasing the python SDK, and following the release similar to java SDK, we need to setup an account for the
cdevents-bot
on the PyPI site so we can use github actions to automate the release of the SDK with each release. @afrittoli do you mind following this link to setup an account for the bot and then setup an API token! Similar to thesecrets.GH_BOT_TOKEN
used in the changelog github action, a new token likesecrets.PYPI_BOT_TOKEN
could be used. Then I can create the automation and work on creating our first release using github actions. Source of how upload our python package.Also there is no rush on this, with the CD Con next week, please take all the time you need! I'm still working on a few automation features while my teammate is working on the pydantic enhancements. Hope you have a great start to May!