[BUG] Fix failing JS CI due to ollama import (#3555) #876
tazarovrelease-chromadb.yml
on: push
check-tag
0s
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
get-version
22s
JavaScript client tests
/
test
3m 16s
Go tests
/
cluster-test
5m 38s
Matrix: python-tests / test-cluster-integration
Deploy docs to Vercel
2m 10s
Publish to DockerHub and GHCR
52s
Publish to PyPI
1m 36s
Release to Chroma Cloud
4s
Annotations
13 warnings
|
check-tag
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):
|
|
Make GitHub release
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Release to Chroma Cloud
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
built-chromadb-package
|
28 MB |
|