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
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-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 thefeast-serving-client
andfeast-datatypes
artifacts 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
The text was updated successfully, but these errors were encountered: