Merge pull request #22 from microsoft/fix/parser-where-whitespace #41
python-publish.yml
on: push
Bump version
6s
Publish to PyPI
22s
Publish to TestPyPI
0s
Annotations
5 warnings
|
Publish to PyPI
Unexpected input(s) 'trusted-publisher', valid inputs are ['user', 'password', 'repository-url', 'repository_url', 'packages-dir', 'packages_dir', 'verify-metadata', 'verify_metadata', 'skip-existing', 'skip_existing', 'verbose', 'print-hash', 'print_hash', 'attestations']
|
|
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
|
|
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
|
|
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
|
|
Publish to PyPI
Unexpected input(s) 'trusted-publisher', valid inputs are ['user', 'password', 'repository-url', 'repository_url', 'packages-dir', 'packages_dir', 'verify-metadata', 'verify_metadata', 'skip-existing', 'skip_existing', 'verbose', 'print-hash', 'print_hash', 'attestations']
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
python-package-distributions
|
135 KB |
sha256:ae96f17c31f4c309c32946ad5bdaebab289211f6854fc229a794575fc24adb0b
|
|