Bump redis from 5.3.1 to 7.0.1 #490
dependabot[bot]checks.yml
on: pull_request
Annotations
2 errors and 44 warnings
|
SonarCloud
Action failed: The process '/opt/hostedtoolcache/sonar-scanner-cli/8.0.1.6346/linux-x64/bin/sonar-scanner' failed with exit code 3
|
|
Check CI Green
Process completed with exit code 1.
|
|
Code Lint (3.14)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Code Lint (3.14)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Code Lint (3.11)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Code Lint (3.11)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Code Lint (3.10)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Code Lint (3.10)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Integration tests (3.14)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Integration tests (3.14)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Integration tests (3.13)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Integration tests (3.13)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Integration tests (3.11)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Integration tests (3.11)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Code Lint (3.13)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Code Lint (3.13)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Integration tests (3.9)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Integration tests (3.9)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Unit Tests (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit Tests (3.12)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Unit Tests (3.12)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Code Lint (3.9)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Code Lint (3.9)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Code Lint (3.12)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Code Lint (3.12)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Integration tests (3.10)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Integration tests (3.10)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Unit Tests (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit Tests (3.10)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Unit Tests (3.10)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Unit Tests (3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit Tests (3.9)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Unit Tests (3.9)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Integration tests (3.12)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Integration tests (3.12)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Unit Tests (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit Tests (3.13)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Unit Tests (3.13)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Unit Tests (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit Tests (3.11)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Unit Tests (3.11)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
Unit Tests (3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit Tests (3.14)
No file matched to [/home/runner/work/py-cachify/py-cachify/**/*requirements*.txt,/home/runner/work/py-cachify/py-cachify/**/*requirements*.in,/home/runner/work/py-cachify/py-cachify/**/*constraints*.txt,/home/runner/work/py-cachify/py-cachify/**/*constraints*.in,/home/runner/work/py-cachify/py-cachify/**/pyproject.toml,/home/runner/work/py-cachify/py-cachify/**/uv.lock,/home/runner/work/py-cachify/py-cachify/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Unit Tests (3.14)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
|
SonarCloud
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, SonarSource/sonarqube-scan-action@v7.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
SonarCloud
Running this GitHub Action without SONAR_TOKEN is not recommended
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
coverage-3.10.xml
|
2.37 KB |
sha256:b54f2a4cb65e25326546f1e2505285dcb10357d21cf98cbd5c13ccb59f83ebb9
|
|
|
coverage-3.11.xml
|
2.37 KB |
sha256:6203f50a8e4b510879ba9d6ba80c0ab2665984fb301c01ce6b80d15a3007ba56
|
|
|
coverage-3.12.xml
|
2.37 KB |
sha256:f3c7e4f8d3998c83aa576f71fe8f6c7cdd3c74f4dbafc937431f9938d0d4f8ae
|
|
|
coverage-3.13.xml
|
2.37 KB |
sha256:e87b3e2032ad12f641e6f725ae7a967d4bcf57cfde2a72ef405a1935a047aca9
|
|
|
coverage-3.14.xml
|
2.36 KB |
sha256:1a3aece3443f0560845b1bc7d4a691309baf3f89d9052cb59d8645165b66d72c
|
|
|
coverage-3.9.xml
|
2.37 KB |
sha256:73fae7bfa0c8742ded882d712c1ce4653ab4eebdb7e91e7858440d789158bbc7
|
|