You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tinkerpop.apache.org by sp...@apache.org on 2023/02/16 18:12:19 UTC

[tinkerpop] 01/03: Update pypi release setup given new use of API tokens by PyPI CTR

This is an automated email from the ASF dual-hosted git repository.

spmallette pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git

commit d91bd8608963c997d1738114912bc4e5df05cb48
Author: Stephen Mallette <st...@amazon.com>
AuthorDate: Thu Feb 16 13:11:18 2023 -0500

    Update pypi release setup given new use of API tokens by PyPI CTR
---
 docs/src/dev/developer/development-environment.asciidoc | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/docs/src/dev/developer/development-environment.asciidoc b/docs/src/dev/developer/development-environment.asciidoc
index 0b029039a8..c202807e6c 100644
--- a/docs/src/dev/developer/development-environment.asciidoc
+++ b/docs/src/dev/developer/development-environment.asciidoc
@@ -347,9 +347,12 @@ username = <username>
 password =
 ----
 
-The release manager shall use the project's pypi credentials, which are available in the
-link:https://svn.apache.org/repos/private/pmc/tinkerpop[PMC SVN repository]. The `password` should be left blank so
-the deployment process in Maven will prompt for it at deployment time.
+The approach above assumes basic authentication and a blank password will in `.pyirc` will have Maven prompt for a
+password. That said, it is preferred that your account be secured with 2FA, in which case, basic authentication will
+no longer be allowed. Instead, an API token is required. It can be generated under your
+link:https://pypi.org/manage/account/token/[account settings] and then the username in `.pyirc` is set to `__token__`
+and the password to the token value. Please see link:https://pypi.org/help/#apitoken[PyPI documentation] for more
+details.
 
 For .NET releases, install link:http://www.mono-project.com/[Mono]. The release process is known to work with 6.12.0,
 so it is best to probably install that version. Release managers should probably also do an install of