Skip to content

ASP-1893: Migrate plugin repo from JFrog to Google Artifact Registry#49

Closed
suresh-prakash wants to merge 1 commit into
mainfrom
fix-publish-workflow
Closed

ASP-1893: Migrate plugin repo from JFrog to Google Artifact Registry#49
suresh-prakash wants to merge 1 commit into
mainfrom
fix-publish-workflow

Conversation

@suresh-prakash

Copy link
Copy Markdown
Contributor

Summary

  • Migrate plugin repository from hypertrace.jfrog.io/artifactory/maven to us-maven.pkg.dev/hypertrace-repos/maven
  • Bump org.hypertrace.version-settings plugin from 0.2.0 to 0.3.0

This fixes the publish workflow failure where JFrog returns a corrupted POM for version-settings-plugin 0.2.0:

[Fatal Error] org.hypertrace.version-settings.gradle.plugin-0.2.0.pom:2:10: Already seen doctype.

Aligns with other hypertrace repos that have already migrated (document-store, kafka-streams-framework, data-model, etc.).

Context

Test plan

  • CI build passes
  • After merge, create release and verify publish workflow succeeds

🤖 Generated with Claude Code

JFrog (hypertrace.jfrog.io) is serving a corrupted POM for
version-settings-plugin 0.2.0, causing publish workflow failures.

Migrate to us-maven.pkg.dev/hypertrace-repos/maven (the new standard)
and bump version-settings plugin from 0.2.0 to 0.3.0, aligning with
other hypertrace repos (document-store, kafka-streams-framework, etc.).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@suresh-prakash

Copy link
Copy Markdown
Contributor Author

Closing — this repo has been moved to Traceableai/kafka-topic-creator. The Traceableai fork already uses Google Artifact Registry and version-settings 0.3.0.

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