Skip to content

fix(publishing): separate Maven namespace deployments - #789

Merged
hdcodedev merged 1 commit into
mainfrom
fix/separate-maven-namespaces
Oct 16, 2026
Merged

hdcodedev merged 1 commit into
mainfrom
fix/separate-maven-namespaces

Conversation

@hdcodedev

Copy link
Copy Markdown
Member

Summary

Maven Central rejected the 3.0.0 release because chart artifacts and relocation POMs were uploaded in one bundle containing two namespaces. Publish chart modules and the BOM first, then publish relocation POMs in a separate Gradle invocation so each deployment contains one namespace.

Local Validation

  • ./gradlew ktlintCheck
  • ./gradlew :charts-<module>:jvmTest
  • ./gradlew chartsTestJvm
  • ./gradlew ciCompile
  • ./gradlew chartsCheck
  • ./gradlew apiCompatibilityCheck
  • ../charts-playground/gradlew -p ../charts-playground -DchartsLocalPath="$PWD" ciCompile
  • ./gradlew :androidApp:validateDebugScreenshotTest
  • ./gradlew updateScreenshots

Additional validation:

  • Passed both publishing task graphs with -PchartsReleaseVersion=3.0.0 -PmavenCentralPublishing=true -PsignAllPublications=true --dry-run --no-daemon: the chart run contains all 11 new-namespace modules and excludes relocation; the relocation run contains only the 10 legacy publications.
  • Checked the composite action with a stub Gradle wrapper for both release and snapshot version arguments.
  • Passed git diff --check. Actual Maven publishing will run in CI.

@hdcodedev
hdcodedev enabled auto-merge (squash) October 16, 2026 22:09
@hdcodedev
hdcodedev merged commit 60864f8 into main Oct 16, 2026
22 checks passed
@hdcodedev
hdcodedev deleted the fix/separate-maven-namespaces branch October 16, 2026 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant