actions/pypi-publish
1
0
Fork 0
mirror of https://github.com/pypa/gh-action-pypi-publish.git synced 2024-11-09 10:23:35 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

README: small doc tweaks

Browse source 
Signed-off-by: William Woodruff <william@trailofbits.com>
This commit is contained in:
William Woodruff 2023-04-24 09:28:57 -06:00
parent f47b34707f
commit 0811f991bd
No known key found for this signature in database
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -31,8 +31,8 @@ tag, or a full Git commit SHA.
> this is what they're referring to. > this is what they're referring to.
This example jumps right into the current best practice. If you want to This example jumps right into the current best practice. If you want to
go for less secure scoped PyPI API tokens, check out [how to specify use API tokens directly or a less secure username and password, check out
username and password]. [how to specify username and password].
This action supports PyPI's [trusted publishing] This action supports PyPI's [trusted publishing]
implementation, which allows authentication to PyPI without a manually implementation, which allows authentication to PyPI without a manually
@ -230,9 +230,9 @@ In the past, when publishing to PyPI, the most secure way of the access scoping
for automatic publishing was to use the [API tokens][PyPI API token] feature of for automatic publishing was to use the [API tokens][PyPI API token] feature of
PyPI. One would make it project-scoped and save as an environment-bound secret PyPI. One would make it project-scoped and save as an environment-bound secret
in their GitHub repository settings, naming it `${{ secrets.PYPI_API_TOKEN }}`, in their GitHub repository settings, naming it `${{ secrets.PYPI_API_TOKEN }}`,
for example. See [Creating & using secrets]. This is no longer encouraged when for example. See [Creating & using secrets]. While still secure,
publishing to PyPI or TestPyPI, in favor of [trusted publishing]. [trusted publishing] is now encouraged over API tokens as a best practice
on supported platforms (like GitHub).
## License ## License