2606.06 Release Artifacts (Community Maven)

Kernel
1

Hi,

I’m working on some A12 tools based on the initial public 2506 release and I’m trying to upgrade to 2606.06 right now.

I’m running into errors bumping the versions to 2606.06 and claude tells me this:

image
image1334×519 48.3 KB

So kernel-md-facade is the only kernel module that actually has 31.1.0 published to this repo — the other five kernel modules and dataservices-core-metadata/base-model-migration-api are missing their matrix-target versions entirely from a12-community-maven. That’s a repo/mirror gap, not something I can work around by picking a different version number.

Is a12-community-maven the right repository for the full 2026.06 release, or is there a separate/newer repo URL you’re supposed to point at for this release train?

Won’t these dependencies released anymore?

2

Hi @Matthias_Faust,
regarding the artifacts, Claude and you are missing:

  • The following artifacts are a12internal: kernel-md-join, kernel-md-combination-model, kernel-structural-mapping-tool, kernel-md-model-migration. I think the use of the Workspace Converter and the dependency to kernel-md-facade should be enough for these artifacts, otherwise please contact the Kernel team directly.
  • I assume that you are using MappingModelCodegenCLI.java from kernel-md-datatransfer-codegen. This class has been moved, see Kernel migration instructions. Here, you have to see if you use the CLI-artifact to generate mapping code since this artifact has been renamed, or if kernel-md-facade is enough as dependency.
  • base-model-migration-api has been removed, see Base migration instructions.
  • dataservices-core-metadata has been removed, see please DataServices migration instructions.

You can tell Claude to have a look at the migration instructions of the A12 components (if you are an enterprise user, you can use the Claude Plugin Marketplace), but be aware that only information related to public API/features are documented there. For a12internal changes, you will have to contact the corresponding component directly.

3

Thanks! I want to stick to public API resources of course. Your answers helped me to do that. So thank you for your quick response!