[RELEASE] 0.4.12 to fix Dockerfile log issue (#1165) #434
HammadB
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
chroma-release.yml
on: push
check_tag
0s
build-and-release
7m 58s
Annotations
7 warnings and 2 notices
|
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. 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.12.tar.gz did not match any files
|
|
build-and-release
Artifact pattern:dist/chroma-0.4.12.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/
|
|
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
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://upload.pypi.org/legacy/
|
|
build-and-release
Using a user-provided API token for authentication against https://test.pypi.org/legacy/
|