A release run executes the publish-java-sdk job successfully and the java artifacts are published.
Current Behavior
For a while there was no successful run for the publish-java-sdk job. The last release of the feast-serving-client and feast-datatypes artifacts are from version 0.38.0: https://central.sonatype.com/namespace/dev.feastf
What is the current plan for the java sdk? Is it possible to fix this pipeline bug and publish the artifacts again? We would like to use it but want to use the most current version to be in sync with the python sdk.
Expected Behavior
A release run executes the
publish-java-sdkjob successfully and the java artifacts are published.Current Behavior
For a while there was no successful run for the
publish-java-sdkjob. The last release of thefeast-serving-clientandfeast-datatypesartifacts are from version 0.38.0: https://central.sonatype.com/namespace/dev.feastfIt seems the last step is failing when the built artifacts are uploaded to the artifact server: https://github.com/feast-dev/feast/actions/runs/11534020401.
Possible Solution
What is the current plan for the java sdk? Is it possible to fix this pipeline bug and publish the artifacts again? We would like to use it but want to use the most current version to be in sync with the python sdk.
Maybe the support page already helps: https://support.sonatype.com/hc/en-us/articles/360049469534-401-Content-access-is-protected-by-token-when-accessing-repositories