Skip to content

[CLN] Remove ChromaResponse in favor of endpoint-specific responses (… #681

[CLN] Remove ChromaResponse in favor of endpoint-specific responses (…

[CLN] Remove ChromaResponse in favor of endpoint-specific responses (… #681

Triggered via push February 24, 2024 03:19
Status Success
Total duration 7m 27s
Artifacts
check_tag
0s
check_tag
build-and-release
6m 53s
build-and-release
Fit to window
Zoom out
Zoom in

Annotations

7 warnings and 1 notice
build-and-release
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, actions/setup-python@v4, docker/[email protected], docker/[email protected], aws-actions/configure-aws-credentials@v1, richardsimko/[email protected], ncipollo/[email protected], actions/github-script@v6. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-and-release
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1, richardsimko/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-and-release
Artifact pattern :dist/chroma-0.4.24.dev13.tar.gz did not match any files
build-and-release
Artifact pattern:dist/chroma-0.4.24.dev13.tar.gz did not match any files
build-and-release
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-release
Input 'repository_url' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `repository-url` instead.
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
build-and-release
Using a user-provided API token for authentication against https://test.pypi.org/legacy/