From 3ffc85ef22905cd1104db605a05366f1e25aad07 Mon Sep 17 00:00:00 2001
From: Eduardo Aguad <edu@aguad.dev>
Date: Sat, 6 Jun 2026 21:43:27 -0400
Subject: [PATCH] Use the org-level PYPI_USERNAME/PYPI_PASSWORD secrets for
 publishing

The repo-level TWINE_USERNAME/TWINE_PASSWORD secrets get a 403 from
PyPI; the PYPI_* names publish successfully from the masonite and orm
repositories.
---
 .github/workflows/pythonpublish.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/pythonpublish.yml b/.github/workflows/pythonpublish.yml
index d3b3c59..4bdfd46 100644
--- a/.github/workflows/pythonpublish.yml
+++ b/.github/workflows/pythonpublish.yml
@@ -18,8 +18,8 @@ jobs:
         # are committed in the repository, so no npm build is needed for a
         # notice-only post release.
         env:
-          TWINE_USERNAME: ${{ secrets.TWINE_USERNAME }}
-          TWINE_PASSWORD: ${{ secrets.TWINE_PASSWORD }}
+          TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
+          TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
         run: |
           python -m pip install --upgrade pip
           pip install setuptools wheel twine