You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Publish GraphCompose to Maven Central (Sonatype OSSRH + GPG signing) #7
Goal. Make GraphCompose available via Maven Central as the primary distribution channel; keep JitPack as a documented fallback.
Why. JitPack is a fast, low-friction default for early releases, but for a Java library targeting production server-side adoption, Maven Central is the authoritative registry: it ships with every build agent, requires no additional <repository> declaration, and signals stability + maturity to Java decision makers.
Coordinates target. From v1.7 onward, the canonical install snippet becomes:
```xml
io.github.demchaav
graphcompose
1.7.0
```
(Note the group-id flip from `com.github.DemchaAV` (JitPack convention) to `io.github.demchaav` (Sonatype namespace). The `groupId` field in the POM already points there.)
Scope.
Sonatype OSSRH account + namespace ownership for `io.github.demchaav`
GPG signing key generated, distributed to public keyserver, and configured in CI secrets
`pom.xml` extended with `distributionManagement`, `maven-source-plugin`, `maven-javadoc-plugin`, `maven-gpg-plugin`
CI workflow that triggers on tag push (`v*..`) and runs `mvn deploy -Prelease` against OSSRH staging
Staging-repo close + release automated via the `nexus-staging-maven-plugin`
README install snippet flips to Maven Central coordinates; JitPack snippet kept as a "fallback" subsection
First Maven Central release tagged as v1.7.0; JitPack continues to mirror the same tag
Out of scope.
Migrating prior tags (v1.0 - v1.6) to Maven Central. Only v1.7+ ships there.
Tracking. Linked to milestone v1.7. CHANGELOG already lists Maven Central as a v1.7 stretch goal under "Phase E".
Staging plugin: nexus-staging-maven-plugin was replaced by the newer central-publishing-maven-plugin (Sonatype's recommended path for the new Central Publisher Portal).
JitPack policy: docs are now Maven-Central-only rather than "Central primary, JitPack fallback". JitPack still mirrors tags but is no longer a documented install path.
CHANGELOG's "Phase E / v1.7 stretch goal" wording is also outdated and should be revised in the next docs sweep.
Activity
docs+ci: post-release polish for v1.6.0 (audit P0+P1)
DemchaAV commentedon May 31, 2026
Closing — shipped in v1.6.6 rather than v1.7, with a few deliberate deviations from the original plan.
Delivered
central-publishing-maven-pluginwired into release profile — build(release): add central-publishing-maven-plugin to release profile (D3) #97 (D3)Deviations from this issue
graphcompose→graph-compose(chore: rename Maven artifactId graphcompose -> graph-compose ahead of Central debut #105). The hyphenated form is what Central debuts with.nexus-staging-maven-pluginwas replaced by the newercentral-publishing-maven-plugin(Sonatype's recommended path for the new Central Publisher Portal).CHANGELOG's "Phase E / v1.7 stretch goal" wording is also outdated and should be revised in the next docs sweep.
post-release: open v1.6.7 cycle; flip status + japicmp baseline to v1…
post-release: open v1.6.7 cycle; flip status + japicmp baseline to v1…