From efef715525a092d648c47c400c7b4f70337d3387 Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Tue, 11 Feb 2025 02:53:31 +0100 Subject: [PATCH] [5.2.x] Specified "django" repository for twine call in docs/internals/howto-release-django.txt. It's necessary to specify a repository for `.pypirc` user configurations with multiple per-project PyPI tokens. Follow up to 26aedbbc0835df83140c7424df62bda03382f598. Backport of 0dc61495b2217e9c5a872ac967dfcf197d342c84 from main. --- docs/internals/howto-release-django.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index b1fb435c48..14329bb455 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -615,7 +615,7 @@ Now you're ready to actually put the release out there. To do this: .. code-block:: shell - $ twine upload dist/* + $ twine upload --repository django dist/* #. Go to the `Add release page in the admin`__, enter the new release number exactly as it appears in the name of the tarball