This is an automated email from the ASF dual-hosted git repository.
husseinawala pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new c16b421872 Remove pypitest from the release process (#36466)
c16b421872 is described below
commit c16b4218728a654c2a9d51a5a637ebf595f20136
Author: Jarek Potiuk <[email protected]>
AuthorDate: Thu Dec 28 10:11:31 2023 +0100
Remove pypitest from the release process (#36466)
---
dev/README_RELEASE_PROVIDER_PACKAGES.md | 37 ++++++---------------------------
1 file changed, 6 insertions(+), 31 deletions(-)
diff --git a/dev/README_RELEASE_PROVIDER_PACKAGES.md
b/dev/README_RELEASE_PROVIDER_PACKAGES.md
index a5a92cbac7..199480c43b 100644
--- a/dev/README_RELEASE_PROVIDER_PACKAGES.md
+++ b/dev/README_RELEASE_PROVIDER_PACKAGES.md
@@ -401,31 +401,13 @@ increased until the tag is not found.
twine check ${AIRFLOW_REPO_ROOT}/dist/*
```
-* Upload the package to PyPi's test environment:
-
-```shell script
-twine upload -r pypitest ${AIRFLOW_REPO_ROOT}/dist/*
-```
-
-If you see
-> WARNING Error during upload. Retry with the --verbose option for more
details.
-ERROR HTTPError: 403 Forbidden from https://test.pypi.org/legacy/
- The user [user_name] isn't allowed to upload to project [provider_name]
-
-It means that you don't have permission to upload providers.
-Please ask one of the Admins to grant you permissions on the packages you wish
to release.
-
-
-* Verify that the test packages look good by downloading it and installing
them into a virtual environment.
-Twine prints the package links as output - separately for each package.
-
-* Upload the package to PyPi's production environment:
+* Upload the package to PyPi:
```shell script
twine upload -r pypi ${AIRFLOW_REPO_ROOT}/dist/*
```
-* Again, confirm that the packages are available under the links printed.
+* Confirm that the packages are available under the links printed and look
good.
## Add tags in git
@@ -1114,22 +1096,15 @@ This is expected, the RC tag is most likely behind the
main branch.
twine check ${AIRFLOW_REPO_ROOT}/dist/*.whl ${AIRFLOW_REPO_ROOT}/dist/*.tar.gz
```
-* Upload the package to PyPi's test environment:
-
-```shell script
-twine upload -r pypitest ${AIRFLOW_REPO_ROOT}/dist/*.whl
${AIRFLOW_REPO_ROOT}/dist/*.tar.gz
-```
-
-* Verify that the test packages look good by downloading it and installing
them into a virtual environment.
- Twine prints the package links as output - separately for each package.
-
-* Upload the package to PyPi's production environment:
+* Upload the package to PyPi:
```shell script
twine upload -r pypi ${AIRFLOW_REPO_ROOT}/dist/*.whl
${AIRFLOW_REPO_ROOT}/dist/*.tar.gz
```
-Copy links to updated packages, sort it aphabeticly and save it on the side.
You will need it for the announcement message.
+* Verify that the packages are available under the links printed.
+
+Copy links to updated packages, sort it alphabetically and save it on the
side. You will need it for the announcement message.
* Again, confirm that the packages are available under the links printed.
