From 97c3ccc5cbf89fd5ad811502d3b1e41d11f875ac Mon Sep 17 00:00:00 2001
From: Pasindu Owa Gamage <pasinduogdev@gmail.com>
Date: Sat, 21 Feb 2026 23:07:41 +0530
Subject: [PATCH] ci: fix maven central 401 unauthorized deployment error

- Changed setup-java server credentials to use environment variable names instead of direct secret values.
- Mapped GitHub secrets to MAVEN_USERNAME and MAVEN_PASSWORD in the deploy step environment.
- Resolves the persistent 401 Unauthorized error during central-publishing-maven-plugin execution.
---
 .github/workflows/build.yml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 03827f7..4ec8c50 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -46,13 +46,15 @@ jobs:
           java-version: '17'
           distribution: 'temurin'
           server-id: central
-          server-username: ${{ secrets.MAVEN_USERNAME }}
-          server-password: ${{ secrets.MAVEN_PASSWORD }}
+          server-username: MAVEN_USERNAME
+          server-password: MAVEN_PASSWORD
           gpg-private-key: ${{ secrets.GPG_PRIVATE_KEY }}
           gpg-passphrase: ${{ secrets.GPG_PASSPHRASE }}
 
       - name: Deploy to Maven Central
         env:
+          MAVEN_USERNAME: ${{ secrets.MAVEN_USERNAME }}
+          MAVEN_PASSWORD: ${{ secrets.MAVEN_PASSWORD }}
           MAVEN_GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
         run: |
           echo "Deploying to Maven Central..."