📦 Release chromadb to PyPI and DockerHub

[RELEASE] JS-Client 1.10.3 (#3488) #825

Sign in to view logs

Re-run triggered January 15, 2025 05:43

itaismith

main

Status Failure

Total duration 15m 29s

Billable time 1h 25m

Artifacts 60

release-chromadb.yml

on: push

Matrix: Go tests / test

Matrix: python-tests / test-single-node-integration-stress

Matrix: python-tests / test-single-node-integration

Matrix: python-tests / test-stress

Matrix: python-tests / test-thin-client

Matrix: python-tests / test

Matrix: Rust tests / test-benches

Matrix: Rust tests / test-integration

Matrix: Rust tests / test

JavaScript client tests / test

Go tests / cluster-test

Matrix: python-tests / test-cluster-integration

Deploy docs to Vercel

python-tests / merge-cluster-logs

Publish to DockerHub and GHCR

Publish to PyPI

Publish thin client to PyPI

Make GitHub release

Release to Chroma Cloud

Annotations

11 warnings

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

get-version

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Deploy docs to Vercel

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

python-tests / merge-cluster-logs

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Publish to DockerHub and GHCR

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Artifacts

Produced during runtime

Name	Size
built-chromadb-package	27.9 MB