ci: release workflow — deploy to Maven Central on tag push#2
Conversation
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Adds
.github/workflows/release.ymlthat fires on tag push (v*) and runsmvn -P release deployto publish to Maven Central. Repository secrets (GPG_PRIVATE_KEY,GPG_PASSPHRASE,MAVEN_CENTRAL_USERNAME,MAVEN_CENTRAL_PASSWORD) are already configured.Why
v0.2.0is already tagged on main but the artifacts aren't on Maven Central — there was no release workflow. This PR adds the missing automation. After merge, re-pushing the tag (or pushing the next tag) will trigger the release.Test plan
mvn verify -Bworkflowv0.2.0tag to trigger the release workflowdev.jamjet:jamjet-cloud-sdk:0.2.0anddev.jamjet:jamjet-cloud-spring-boot-starter:0.2.0