Notes on what is needed for pypi packages.

1. An account needs to be created for Pypi and Test Pypi (separately). Account requires name, email, and password so need to determine who from CFPB will control that account.
2. To generate API tokens, you have to set 2FA. This means using Google Authenticator or some other app (I used GA)
3. API tokens can be generated per package or for the entire account. I found generating tokens on a per package basis less problematic and apparently is the preferred approach.
4. I was not able to get poetry to publish regtech-regex nicely because of the yaml file we include. Hatch worked easily. So for regtech-regex, doing brew install hatch and using it is preferred.
5. API tokens can be set as environment variables using HATCH_INDEX_AUTH=<token> with a HATCH_INDEX_USER=__token__
6. Publishing does not allow overwriting existing published packages, so either you have to remove the existing, or always increment the version number
7. Steps to build and publish are simply:
   a. hatch build
   b. hatch publish -r test