Skip to content
🤖 Repository DevOps Automation

Chore: Re-jig PyPI publishing to use API tokens (not deprecated metho… #86

Sign in to view logs

Chore: Re-jig PyPI publishing to use API tokens (not deprecated metho…

Chore: Re-jig PyPI publishing to use API tokens (not deprecated metho… #86

Triggered via push August 5, 2024 15:46
@ModeSevenIndustrialSolutionsModeSevenIndustrialSolutions
pushed bb44680
main
Status Success
Total duration 3m 2s
Artifacts 1

repository.yaml

on: push
Inspect Repository
3s
Inspect Repository
Gather Workflow Metadata
1s
Gather Workflow Metadata
Python Project
3s
Python Project
Matrix: Python Build
Matrix: Jupyter Notebooks
Matrix: Security Audit
Test Package Publishing
25s
Test Package Publishing
Publish to GitHub
3s
Publish to GitHub
Publish Package
0s
Publish Package
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Test Package Publishing
Input 'print_hash' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `print-hash` instead.
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

Artifacts

Produced during runtime
Name Size
main
17.2 KB