Add Maven Central credentials to publish_release workflow

[mateuszkwiecinski]

No description provided.

[github-actions]

Diffuse output:

OLD: diffuse-base-file
NEW: keeper-gradle-plugin.jar

       │          compressed          │         uncompressed         
       ├───────────┬───────────┬──────┼───────────┬───────────┬──────
 JAR   │ old       │ new       │ diff │ old       │ new       │ diff 
───────┼───────────┼───────────┼──────┼───────────┼───────────┼──────
 class │ 109.3 KiB │ 109.3 KiB │  0 B │ 214.9 KiB │ 214.9 KiB │  0 B 
 other │   5.3 KiB │   5.3 KiB │  0 B │  11.3 KiB │  11.3 KiB │  0 B 
───────┼───────────┼───────────┼──────┼───────────┼───────────┼──────
 total │ 114.6 KiB │ 114.6 KiB │  0 B │ 226.2 KiB │ 226.2 KiB │  0 B 

 CLASSES │ old │ new │ diff      
─────────┼─────┼─────┼───────────
 classes │  72 │  72 │ 0 (+0 -0) 
 methods │ 553 │ 553 │ 0 (+0 -0) 
  fields │ 118 │ 118 │ 0 (+0 -0)

[Copilot]

Pull request overview

This PR adds Maven Central credentials to the publish_release GitHub Actions workflow to enable publishing releases to Maven Central. The credentials are sourced from GitHub secrets and passed to Gradle as environment variables using the ORG_GRADLE_PROJECT_ prefix convention, which is consistent with how signing credentials are already configured in the same workflow.

Changes:

• Added OSSRH_USERNAME and OSSRH_PASSWORD secrets as Gradle properties for Maven Central authentication

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.