Skip to content
PyPI

Fix: Fix handling of 400 response when refreshing token (#38) #46

Sign in to view logs

Fix: Fix handling of 400 response when refreshing token (#38)

Fix: Fix handling of 400 response when refreshing token (#38) #46

Triggered via push January 30, 2024 20:50
@glenscglensc
pushed 45badb2
3.4.28
Status Success
Total duration 49s
Artifacts –

pypi.yml

on: push
Publish to PyPI
42s
Publish to PyPI
Fit to window
Zoom out
Zoom in

Annotations

2 warnings and 1 notice
Publish to PyPI
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Publish to PyPI
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/