chore(deps): update dependency djangorestframework to v3.17.1 #16342
Triggered via pull request
April 15, 2026 07:49
renovate[bot]
Status
Success
Total duration
2h 18m 36s
Artifacts
3
bleeding.yml
on: pull_request
ci
/
revisions
3s
ci
/
Anchore Container Scan
2m 20s
ci
/
Trivy Container Scan
2m 36s
ci
/
...
/
Test container basic, bleeding
7m 49s
ci
/
...
/
Test container anubis, bleeding
7m 15s
ci
/
...
/
Test container read-write, bleeding
8m 36s
ci
/
...
/
Test container localtime, bleeding
9m 32s
ci
/
...
/
Test container saml, bleeding
7m 58s
ci
/
...
/
Test container split, bleeding
8m 50s
ci
/
...
/
Test container celery-single, bleeding
7m 47s
ci
/
...
/
Test container basic, bleeding
10m 50s
ci
/
Publish to Docker Hub, ${{ inputs.variant }}
0s
ci
/
Publish to GitHub, ${{ inputs.variant }}
0s
Annotations
4 warnings
|
ci / buildx / Build, bleeding, arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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/
|
|
ci / build / Build, bleeding, amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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/
|
|
ci / Anchore Container Scan
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
|
|
ci / Trivy Container Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Docker cache amd64
Expired
|
813 MB |
sha256:8b4dda18e92cb121cf983586aa887ba1a7be72e03546cb3005496ee2cf998787
|
|
|
Docker cache arm64
Expired
|
795 MB |
sha256:04769e514cbd6c0ef4e6cb82e2f0f61ce0090f652f9fc95fccea29e3d639f2fb
|
|
|
Trivy scan SARIF
|
8.14 KB |
sha256:477adcf7a9ca3cb613678275d582d2ebb2c2710d9af588747c4e1750d8ade600
|
|