chore(deps): update weblate/base docker tag to v2026.19.0 (#4504) #16525
bleeding.yml
on: push
ci
/
revisions
3s
ci
/
Anchore Container Scan
2m 1s
ci
/
Trivy Container Scan
2m 10s
ci
/
...
/
Test container basic, bleeding
8m 28s
ci
/
...
/
Test container anubis, bleeding
8m 35s
ci
/
...
/
Test container read-write, bleeding
8m 23s
ci
/
...
/
Test container localtime, bleeding
8m 14s
ci
/
...
/
Test container saml, bleeding
8m 28s
ci
/
...
/
Test container split, bleeding
8m 40s
ci
/
...
/
Test container celery-single, bleeding
8m 15s
ci
/
...
/
Test container basic, bleeding
11m 23s
ci
/
Publish to Docker Hub, bleeding
2m 23s
ci
/
Publish to GitHub, bleeding
2m 36s
Annotations
3 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
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Docker cache amd64
|
987 MB |
sha256:af05a1cf3b69049d524e7d39850acb5dc156b68d6da75c97d4e4cbbab6efbcf1
|
|
|
Docker cache arm64
|
960 MB |
sha256:ed11cc1cdacff95cb3895a71a19d651be79c9d183ca05e4abb3deba2b8fa5316
|
|
|
Trivy scan SARIF
|
18.3 KB |
sha256:3558f28852b70190b573c20cd3a2c3c627ebe0a743e1736055aa0ab0946a5eb5
|
|