promote OSSRH staging to Central Portal from CodeBuild

[cb-jit-bhuin]

Summary

• After maven-publish uploads artifacts, POST /manual/upload/defaultRepository/com.chargebee from the same CodeBuild IP so the staging repo is transferred to the Central Publisher Portal. Gradle PUTs alone do not appear in Deployments or on Maven Central.

Updates the CodeBuild workflow to install AWS CLI v2 and promote published Maven artifacts by POSTing a base64-encoded credential token to /manual/upload/defaultRepository/com.chargebee.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues
✅	Secrets	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: be4df07d-8a4c-4822-815e-93f4b8f743f0

📥 Commits

Reviewing files that changed from the base of the PR and between d928e91 and c5e5433.

📒 Files selected for processing (1)

• build-config/buildspec-prod.yml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

Walkthrough

The production build now sends a base64-encoded Maven credential token to the Sonatype staging upload endpoint after publishing the Maven release. The request fails when Sonatype returns an unsuccessful response.

Changes

Sonatype staging upload

Layer / File(s)	Summary
Add staging upload request build-config/buildspec-prod.yml	The release workflow encodes Maven credentials, sends a Bearer-authorized POST request to Sonatype, and fails on unsuccessful HTTP responses.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: 🔵 Low · up to c5e54

The change promotes published artifacts to the Central Portal using the existing Maven credentials. If those secrets are still legacy OSSRH tokens, publication may succeed while promotion fails and require manual cleanup; confirm the configured credentials before merging.

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

---

_{Comment @coderabbitai help to get the list of available commands.}