refactor(redis): simplify Redis client initialization logic #174
tanbroAnnotations
10 warnings
|
unittest-linux (3.11)
Could not parse version from /home/runner/work/redis_func_cache/redis_func_cache/pyproject.toml. Using latest version.
|
|
unittest-linux (3.10)
Could not parse version from /home/runner/work/redis_func_cache/redis_func_cache/pyproject.toml. Using latest version.
|
|
unittest-linux (3.13)
Could not parse version from /home/runner/work/redis_func_cache/redis_func_cache/pyproject.toml. Using latest version.
|
|
unittest-linux (3.14)
Could not parse version from /home/runner/work/redis_func_cache/redis_func_cache/pyproject.toml. Using latest version.
|
|
unittest-linux (3.12)
Could not parse version from /home/runner/work/redis_func_cache/redis_func_cache/pyproject.toml. Using latest version.
|
|
unittest-linux (3.9)
Could not parse version from /home/runner/work/redis_func_cache/redis_func_cache/pyproject.toml. Using latest version.
|
|
unittest-macos
Could not parse version from /Users/runner/work/redis_func_cache/redis_func_cache/pyproject.toml. Using latest version.
|
|
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):
|
|
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
|
|
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.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
redis_func_cache-dist-0.7.a1
Expired
|
125 KB |
sha256:d71ae64ed3b36af2915d99eb99f8ef1b2eb860ff5356fee8503b6655345e9faf
|
|