ci(publish): add Maven Central publishing to release workflow#19
Merged
kperry-godaddy merged 1 commit intomainfrom Mar 6, 2026
Merged
ci(publish): add Maven Central publishing to release workflow#19kperry-godaddy merged 1 commit intomainfrom
kperry-godaddy merged 1 commit intomainfrom
Conversation
jhateley-godaddy
force-pushed
the
ci-publish-to-maven-central
branch
from
9982e25 to
e800fc1
Compare
kperry-godaddy
approved these changes
Mar 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces workflow automation for publishing to Maven Central upon a successful release, improves documentation clarity, and ensures proper build task dependencies for generated code. The most important changes are grouped below:
CI/CD Automation:
publishjob to.github/workflows/release.ymlthat publishes artifacts to Maven Central, triggered only when a release is created by therelease-pleasejob. This includes setting up JDK, GPG, and securely passing credentials.release_created,tag_name, andversionas outputs from therelease-pleasejob for downstream workflow steps.Build Process Improvements:
ans-sdk-api/build.gradle.ktsto ensuresourcesJarandjavadocJartasks depend on code generation (openApiGenerate), preventing build issues with missing generated sources.Documentation Enhancements: (required for publish)
AnsClientto clarify the reference toDiscoveryClientas being from the discovery module.<caption>to the DNS resolver configuration table in theDnsResolverConfigJavadoc f