Upload to pypi has failed

[yarikoptic]

while releasing 0.12.0 which was tagged/released on github, has failed to get uploaded to pypi:

https://github.com/dandi/dandi-schema/actions/runs/19543098102/job/55954635489

removing build/bdist.linux-x86_64/wheel
Successfully built dandischema-0.12.0.tar.gz and dandischema-0.12.0-py3-none-any.whl
Uploading distributions to https://upload.pypi.org/legacy/
Uploading dandischema-0.12.0-py3-none-any.whl
25l
  0% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0.0/128.6 kB • --:-- • ?
  0% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0.0/128.6 kB • --:-- • ?
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 128.6/128.6 kB • 00:00 • 8.7 MB/s
25hWARNING  Error during upload. Retry with the --verbose option for more details. 
ERROR    HTTPError: 403 Forbidden from https://upload.pypi.org/legacy/          
         Invalid or non-existent authentication information. See                
         https://pypi.org/help/#invalid-auth for more information.              
Error: Process completed with exit code 1.

@candleindark @CodyCBakerPhD aware of any potentially related changes which triggered that so we do not just try blindly to reupload now that we moved it under dandi org (happened after the failed attempt)

[yarikoptic]

I guess someone already working on this since we got a new key from a few minutes ago

?

[CodyCBakerPhD]

Copyied/pasted from element.io:

Tokens will have to be updated following the ownership transfer

Though I notice that repo is also using a legacy upload mechanism?

Might want to update altogether: i.e., dedicated workflow or trusted publisher (haven't tried this yet myself)

[yarikoptic]

thanks! we are using auto and apparently pinned it awhile back... I will propose PR to update the pin.

[yarikoptic]

And with #346 now we got to E2BIG issue originally due to too much of change log but in this case might be due to my forced addition of exec for twine. I will review and likely just perform trailing release actions (twine and schema snapshot) manually for this one

[yarikoptic]

I believe we addressed it but then I introduced bugs in

• chore: refactor release action to move schemata related code into scripts #349
  yet to fix up for the next .patch release which should then really confirm that we are done here